Open traversc opened 4 years ago
Hi, RFC32 is stable so it cannot be changed. The process to update the spec is to fork the stable one in a new RFC number, mark it as draft, and make the changes there. And then update the implementations.
I could give it a shot and create a draft. What do you think of the suggested change itself?
The spec doesn't allow for arbitrary number of bytes, but it could be easily modified to handle it.
In fact, there is enough information in just the
size
parameter to determine encoding and decoding of non-multiple of 4s, and you wouldn't need to change the encoding dictionary at all.In my implementation, I handle non-multiple of 4s at the end of the loop as follows:
Encode side:
Decode side: