Skip to content

Tracking issue for constructor tearoffs #46228

Closed
@eernstg

Description

@eernstg

This issue tracks the implementation of the constructor tearoffs feature.

Prerequisite Tasks

Implementation Tasks

  • Issue for language tests written.
    Issue for core library updates.
    Issue for implementation in CFE.
    Issue for implementation in DDC.
    Issue for implementation in the VM.
    Issue for implementation in Dartfmt.
    Issue for implementation in build systems and Angular compiler.
    Issue for VM Service support.
    Issue for implementation in Dartdoc.
  • Issue for implementation in syntax highlighters
  • Issue for support in linter.
    Issue for implementation in IntelliJ.
    Issue for implementation in Cider.
    Issue for tests validated as passing (this is managed via the constructor-tearoffs spreadsheet).
    Issue for web debugging support.
    Issue for implementation in dart2js.
    Issue for implementation in Kythe.
    Issue for implementation in Analyzer.
    Issue for documentation.

Activity

7 remaining items

lrhn

lrhn commented on Jun 14, 2021

@lrhn
Member

The proposal is accepted and available as a feature specification in the "accepted/" directory.

The experiment flag is called "constructor-tearoffs" even if there are other related features included.

added
implementationTrack the implementation of a specific feature (use on area-meta issue, not issues for each tool)
on Jul 29, 2021
devoncarew

devoncarew commented on Aug 24, 2021

@devoncarew
Member

Note that the github project we're using to track this work is here: https://github.com/orgs/dart-lang/projects/27.

eernstg

eernstg commented on Aug 26, 2021

@eernstg
MemberAuthor

@stereotype441, I approved the test failures on language/constructor/explicit_instantiation_syntax_test.dart with a reference to this issue, because the parser is shared between the CFE and the analyzer (so it's a very global thing).

added
P1A high priority bug; for example, a single project is unusable or has many test failures
on Oct 14, 2021
devoncarew

devoncarew commented on Nov 1, 2021

@devoncarew
Member

An update - all work here (modulo documentation) is complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

P1A high priority bug; for example, a single project is unusable or has many test failuresarea-metaCross-cutting, high-level issues (for tracking many other implementation issues, ...).implementationTrack the implementation of a specific feature (use on area-meta issue, not issues for each tool)

Type

No type

Projects

No projects

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @devoncarew@lrhn@eernstg@jcollins-g

      Issue actions

        Tracking issue for constructor tearoffs · Issue #46228 · dart-lang/sdk