Remove support for deprecated leading new in comment references #3529
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The syntax,
[new Foo]
and[Foo.Foo]
have long been deprecated. The analyzer reports[new Foo]
as well, suggesting to replace with[Foo.new]
. This Change removes the support for the deprecated syntaxes.All examples in tests have been changed to
[Foo.new]
. There are also tests for the disambiguation of a constructor and an instance field with the same name which is allowed), e.g. in[Foo.foo]
. The supported disambiguation hint is to add trailing parentheses:[Foo.foo()]
to indicate the constructor.Fixes #3531
Contribution guidelines:
dart format
.Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.