Change:
// Black and White have the same discriminator value ... enum Color { <ins> //~^ ERROR discriminant value `0` assigned more than once </ins> Red = 0xff0000, Green = 0x00ff00, Blue = 0x0000ff, Black = 0x000000, <del> White = 0x000000, //~ ERROR discriminant value `0` already exists </del> <ins> White = 0x000000, </ins> } fn main() { }

Discussion:
<!-- Thank you for filing a bug report! Please provide a short summary of the bug, along with any information you feel relevant to replicating the bug. If you cannot produce a minimal reproduction case (something that would work in isolation), please provide the steps or even link to a repository that causes the problematic output to occur. --Given the following code: <!-- Please provide a link to -- The current output is: <!-- The following is not always necessary. --Ideally the output should look like: I don't have any understanding of the internal machinery of the diagnostics, but it seems that the value is being cast to the unsigned variant of the integer before displayed (in this case -). Of course, the discriminant does its job just fine, and explicitly casting to an also works as expected, only the diagnostics are a bit unfortunate. Changing to in the example causes it to underflow close to which may seem a little intimidating to a newer user who accidentally stumbles on this :smile: The output is the same on both Stable and Nightly <!-- TRIAGEBOTSTART --<!-- TRIAGEBOTASSIGNSTART --<!-- TRIAGEBOTASSIGNDATASTARTTRIAGEBOTASSIGNDATAEND --<!-- TRIAGEBOTASSIGNEND --<!-- TRIAGEBOTEND --
Gave it some more thought, and I'm guessing just evaluates to (and vice-versa for the other integer types) under the hood, but due to consistent wrapping behavior and two's complement, there is no difference to the user since they have to explicitly cast the enum to the respective integer to read it anyway. Well except for this error message I guess.
So I got curious and decided to check out what causes this. Looking around a bit trying to find which part of type-checking had to do with enums led me to this . At the end we there is a part where we go through all the discriminants and ensure none of them are duplicates, and if there are duplicates we emit the E0081 error pointing to the duplicates and all that. <details<summaryThe code</summary</detailsHowever, the type of the is being tracked correctly with respect to any . I a print statement and sure enough: The type of the discriminant is understood to be i8, but the value is expressed as a u8. If I can find a nice solution to this i'll submit a PR.

Honestly, I think this error could probably be reworded as well; since doesn't have an explicitly defined discriminant, we should also clarify that it's used by counting up from the previously defined discriminant, which here is . Of course, that doesn't have to be part of the first PR, but I figure it's worth mentioning here.
Yeah that would improve the error quality in this case. I haven't checked if we can infer from context whether the discriminant has been explicitly assigned or not, but I assume we can, and in that case whenever we detect a duplicate we could add a small note saying that that the implicit discriminant is just a += 1 from the previous discriminant as you say. Doesn't hurt to do that for both positive and negative discriminant duplicates. Anyway I've got something in the works, I'll explore adding this note aswell as soon as I can get back to my computer with some spare time. claim
You should be able to assume that it's been previously assigned, since if every discriminant were inferred, there wouldn't be conflicts, unless the number of variants overflows the type (which I think has a separate error? I'm not actually sure) And I think a good example to test here would be: Since the discriminant for would be actually 3, and fail.
Oh, I meant inferring if whether the duplicate discriminant was explicitly set or not. In the above example, that would be detecting if was assigned explicitly or not. But yeah it was possible, HIR has all the information we need. So here's what I currently have. An enum like this: Errors as such: Not sure about the note. We could split it out with its own span and point to which variant the duplicate increment ( in this case) is incremented from, but i feel like that is unnecessarily verbose. Thoughts? Also I reworded some of the original error message, hopefully it's clearer this way? If not i can revert that. Edit: Sorry i didn't read your comment properly :smiley: . Yeah i guess we could iterate backwards until we hit the first defined discriminant, and point to that in the note.

Yeah, in that case I'd say something like: discriminant is computed as (specified) + N variants later = (duplicate)
Ok, I think I'll leave the notification for another PR :disappointed: . The reason is that in the duplicate-detection loop, we are only storing the type as we go, and not the HIR representation of the variant. This means that (unless I'm missing something) we can't iterate backwards after we hit a duplicate with no assigned discriminant, to the last discriminant assigned explicitly. As an example, for this enum: In the loop, once we get to we compare it to the previously approved discriminants, and detect that is a duplicate of . We want to point to as the "increment startpoint", but we've ditched the HIR information at this point for the approved discriminants (which V2 is part of). Ofcourse we could just loop through all of the variants all over with the HIR included, but that is really inelegant (and ineffecient). So what we should do is re-write the loop but I don't feel like messing with that right now.
Yeah, I think it's totally reasonable to just fix the extremely obvious bug of reinterpreting the integer before tackling the larger issue of the message being weird to begin with. I mostly just wanted to add my thoughts here for a potential solution so anyone else looking to help with this has some ideas to work with.
(Should I create a separate issue for my other suggestions, or would it make sense to reopen this issue until those errors are also fixed?)
It would make sense to me to make a new issue specifically for the stuff we missed from this PR? There are probably good reasons to just go through the entire function. Here's one of the small (possible) imrovements: the check in could probably be done so that we don't have to do two passes?
Alright, filed! Future discussion can go there.