I had an idea that I was going to put in #12 but because that has already ballooned in scope, I'm putting it here instead. These changes, if we choose to go forward with them, would most likely be part of that reworking.
The more I work with this repository the more dissatisfied I am with using nested <byte> tags for two byte tokens.
Here's an abstracted view of the current structure:
I propose changing byte in the first byte of the two-byte case to two-byte (this name I'm not sure about), and every other occurrence of byte to token. What is currently called token should really never have been called token and instead should be version:
I had an idea that I was going to put in #12 but because that has already ballooned in scope, I'm putting it here instead. These changes, if we choose to go forward with them, would most likely be part of that reworking.
The more I work with this repository the more dissatisfied I am with using nested
<byte>
tags for two byte tokens.Here's an abstracted view of the current structure:
I propose changing
byte
in the first byte of the two-byte case totwo-byte
(this name I'm not sure about), and every other occurrence ofbyte
totoken
. What is currently calledtoken
should really never have been calledtoken
and instead should beversion
:I think this communicates what we want much better.