Skip to content

Disable automatic const insertion in analyzer #32819

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dgrove opened this issue Apr 8, 2018 · 4 comments
Closed

Disable automatic const insertion in analyzer #32819

dgrove opened this issue Apr 8, 2018 · 4 comments
Assignees
Labels
legacy-area-analyzer Use area-devexp instead. P1 A high priority bug; for example, a single project is unusable or has many test failures
Milestone

Comments

@dgrove
Copy link
Contributor

dgrove commented Apr 8, 2018

disable automatic const insertion in analyzer - CL is done, scheglov needs to un-revert it.

(This is part of the work for finishing optional new/const)

@dgrove dgrove added P1 A high priority bug; for example, a single project is unusable or has many test failures legacy-area-analyzer Use area-devexp instead. labels Apr 8, 2018
@dgrove dgrove added this to the Dart2 Beta 3 milestone Apr 8, 2018
@bwilkerson bwilkerson assigned bwilkerson and unassigned scheglov Apr 8, 2018
@bwilkerson
Copy link
Member

I think there's been some confusion between two separate pieces of work. I have a CL to make the optional new and const support in analyzer match the latest spec. Konstantin has a CL to make server stop adding const in places where it isn't necessary (which will need to be updated to match the latest spec). Sorry if I caused the confusion.

@bwilkerson
Copy link
Member

@Hixie
Copy link
Contributor

Hixie commented Apr 10, 2018

I don't quite understand this bug... the analyzer will still tell people to add const where they've omitted new but where const would be possible, right?

@bwilkerson
Copy link
Member

We can (if we don't already) have a lint for that, but this issue isn't about what advice the analyzer gives, but rather how it understands what the user has actually written. The analyzer originally implemented an earlier version of the optional new and const proposal; this issue was about making it consistent with the newer version that the CFE had implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-analyzer Use area-devexp instead. P1 A high priority bug; for example, a single project is unusable or has many test failures
Projects
None yet
Development

No branches or pull requests

4 participants