-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[discuss] stage 3 proposals, yay or nay? #670
Comments
I'm game 👍 |
I guess we could also use parse for atob? |
If and when we implement that, yes :-) I said in #16 I see no problem with adding DOMException but it kinda is slippery-sloping into web territory. |
Right. We could have some "minimal web API helpers" thing perhaps? Or we can just have those be implemented by embedders and that's that. IIRC bjson already exports everything necessary for implementing structuredClone... Shall we close #16? |
I don't know, the argument that every embedder ends up implementing them anyway is still valid. I'll work on arraybuffer-base64 and if afterwards atob turns out to be very easy to layer on top, then I guess we might as well do it. Given the choice, most users will probably pick more features over fewer features. |
Good point. |
Did we ever settle on a policy on what to add when?
There's https://github.com/tc39/proposal-arraybuffer-base64 that I'd like to implement because:
uint8array-base64
)1 Lets me remove the hand-rolled base64 parser I added in a1d1bce
The text was updated successfully, but these errors were encountered: