Skip to content
This repository has been archived by the owner on Nov 20, 2024. It is now read-only.

fix issue in const error handling #1045

Merged
merged 3 commits into from
Jun 27, 2018
Merged

Conversation

a14n
Copy link
Contributor

@a14n a14n commented Jun 27, 2018

No description provided.

Copy link
Member

@pq pq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! Is there an easy test case we can add that flags what was missed previously?

@pq
Copy link
Member

pq commented Jun 27, 2018

% travis failure this looks awesome. Thanks for the quick follow-up!

@a14n
Copy link
Contributor Author

a14n commented Jun 27, 2018

It looks like some errors can not be used to create AnalysisError. For instance analyzer shows no error for new AnalysisError(null, null, null, CompileTimeErrorCode.AMBIGUOUS_EXPORT) but fails at runtime with --enable-asserts.

@pq pq merged commit 0baadb2 into dart-lang:master Jun 27, 2018
@pq
Copy link
Member

pq commented Jun 27, 2018

@a14n: should I push out a new release w/ this fix?

@a14n a14n deleted the fix-const-handling branch June 27, 2018 14:44
@a14n
Copy link
Contributor Author

a14n commented Jun 27, 2018

@pq go for a new release (dart-lang/sdk#33647 been related to analyzer it shouldn't impact linter)

@pq
Copy link
Member

pq commented Jun 27, 2018

Will do. Thanks!

@bwilkerson
Copy link
Member

... analyzer shows no error for new AnalysisError(null, null, null, CompileTimeErrorCode.AMBIGUOUS_EXPORT) but fails at runtime with --enable-asserts.

The messaging is poor, but that happens when the error expects arguments and none are provided.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants