Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings
This repository was archived by the owner on Jan 25, 2022. It is now read-only.
This repository was archived by the owner on Jan 25, 2022. It is now read-only.

Should “optional new” be implemented? #22

Copy link
Copy link
Closed
Closed
Should “optional new” be implemented?#22
Copy link

Description

@claudepache
claudepache
opened on Jul 26, 2017
Issue body actions

That is:

new Foo?.()

The ongoing refactoring of Issue #20 will not allow that construct at first, because that would add complications in the grammar, and it is practically unused in CoffeeScript (#17). So, it is probably not worth.

However, If you have strong use cases for new, please share them

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
    Morty Proxy This is a proxified and sanitized view of the page, visit original site.