Open wcampbell0x2a opened 5 months ago
Remove support for defining both id = 1 and having a discriminant
I'm not convinced yet we want to do this as it removes some flexibility (what if I want to read/write some arcane binary format, but use it differently/idiomatically in Rust). One example would be identifiers like 0xAB + 1, 0xAB + 2, ...
but in Rust I'd like to represent these as 1, 2, ...
Alternatively, maybe it's best to say "deku will use the attribute id
if specified, else it will use the discriminant` wdyt?
Remove support for defining both id = 1 and having a discriminant
I'm not convinced yet we want to do this as it removes some flexibility (what if I want to read/write some arcane binary format, but use it differently/idiomatically in Rust). One example would be identifiers like
0xAB + 1, 0xAB + 2, ...
but in Rust I'd like to represent these as1, 2, ...
Alternatively, maybe it's best to say "deku will use the attribute
id
if specified, else it will use the discriminant` wdyt?
Agreed, when I have time to return to this I'll implement that.
id = 1
and having a discriminantCloses #306