You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since JSON.stringify() is defined, toUint8Array() or toByteIterator() would be useful for consumption by cryptographically safe (sha256) or fast (ahash) hashing functions.
The text was updated successfully, but these errors were encountered:
toUint8Array and toByteIterator are not currently defined by the spec while JSON.stringify is defined by the spec and this is main reason we have to define its interaction with Record & Tuple.
If you are looking to propose toUint8Array and toByteIterator you would also need to define it related to objects and other common exisitng values in the language, which is definitely not the aim of this proposal. I will classify this as a follow-on proposal goal, if toUint8Array and toByteIterator were to be specified, we would definitely like to see how they interact with Record & Tuple (and also Boxes).
As for #218, it is already a potential follow-on proposal as-is.
In order to focus on changes that are necessary to finish this proposal, we are closing issues related to follow-on proposals. You are free to continue the discussion here and reference it in other venues.
Since JSON.stringify() is defined, toUint8Array() or toByteIterator() would be useful for consumption by cryptographically safe (sha256) or fast (ahash) hashing functions.
The text was updated successfully, but these errors were encountered: