Accomodate Enum init deprecation #6368
Merged
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.
PR dlang/dmd#7996 is modifying the compiler to comply with the language specification:
The current behavior is to assign the value
0to the first enum member when no assign expression is given. The referenced PR introduces a deprecation message when an enum's base type's.initmember is not 0. This applies to the typesdouble,charandreal. This allows applications to maintain the current behavior for a time until the deprecation is over and the behavior will change to match the specification. Note that this means you cannot currently create an enum with base typedouble,charorrealwithout a deprecation message unless you give it's first member an explicit assignment. Since phobos treats deprecations as errors, this PR provides explicit assignments in these cases during this deprecation period.