-
Notifications
You must be signed in to change notification settings - Fork 460
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
js api: improve definition of error objects #810
Labels
Comments
@Ms2ger , can you see if this has been addressed and close this issue if not? |
There has been no attempt to address this. |
I'm working on it. |
Ms2ger
added a commit
to Ms2ger/spec
that referenced
this issue
May 22, 2019
This at least gets somewhat close to defining what's actually intended. Fixes WebAssembly#810.
Ms2ger
added a commit
to Ms2ger/spec
that referenced
this issue
May 27, 2019
This at least gets somewhat close to defining what's actually intended. Fixes WebAssembly#810.
littledan
pushed a commit
that referenced
this issue
Sep 11, 2019
This at least gets somewhat close to defining what's actually intended. Fixes #810.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
There's
[LegacyNamespace=WebAssembly] interface CompileError { };
and then a bunch of prose requirements on the objects that are constructed because of that IDL. AFAICT the only thing that the IDL is supposed to do is define that the namespace object has properties calledFooError
. Let's just do that manually and avoid the conflict?The text was updated successfully, but these errors were encountered: