Fix enum representationsto show correct (implicit) args, const #3669
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.
When adding support for enhanced enums, I think I overlooked some validation of "old scool" enums-with-implicit-constructors. I discovered this when trying to move all tests to use Dart Language version 3.2.0 (next PR).
Unfortunately, the analyzer's
constantInitializer
property for such enum values is not really meant for re-constructing what a constant's source was, and it returns code likeE()
for the constant initializer forE.one
givenenum E { one, two; }
. (It should implicitly use an index of 0, and showE(0)
; see the de-sugaring examples in the spec.) I filed dart-lang/sdk#54988.In this code, we also add the word
const
to enhanced enum values (with an explicit constructor); previously, only old-school enums had the keywordconst
. So now that's unified.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.