Closed
Description
This issue tracks the implementation of the constructor tearoffs feature.
Prerequisite Tasks
- Issue for acceptance of constructor tearoffs feature specification.
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
- highlight.js support (api.dart.dev, api.pub.dev, Dartdoc):
- CodeMirror support (DartPad).
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.
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
No branches or pull requests
Activity
7 remaining items
lrhn commentedon Jun 14, 2021
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.
devoncarew commentedon Aug 24, 2021
Note that the github project we're using to track this work is here: https://github.com/orgs/dart-lang/projects/27.
eernstg commentedon Aug 26, 2021
@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).call
of function object #47147devoncarew commentedon Nov 1, 2021
An update - all work here (modulo documentation) is complete.