feat: Annotate the enum constructor field instead of the class

[oSumAtrIX]

Currently usage:

More intuitive usage:

The compiler plugin will have to check if the class that is instantiated with the annotated field is an enum.

[rushiiMachine]

This doesn't really make sense, also it would introduce global state since I would have to make sure no duplicate FromValues are present on other fields. Not going to be doing this

[oSumAtrIX]

This doesn't really make sense

Please elaborate

also it would introduce global state since I would have to make sure no duplicate FromValues are present on other fields.

This is an implementation difficulty and not an issue with the feature itself.

[rushiiMachine]

This is for matching and returning enum variants, and annotating a single field doesn't make sense since it's not based on that single field, the generated method is on the entire class

[oSumAtrIX]

since it's not based on that single field.

The annotation wants you to specify a single field though because it generates the code around that field.

the generated method is on the entire class

Annotating a field does not prevent generating code using the class the field is in.

Annotating the field saves the user from issues like accidentally renaming the field without changing the name in the annotation. Additionally, annotating the field precisely shows that FromValue is generated by comparing the annotated field. Additionally, it simplifies usage because now you do not have to automatically default to the first field, which is an arbitrary decision that you can only guess, nor have to specify the field you want to match to get the correct enum variant as you'd be annotating the field directly.