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
I can't for the life of me figure out how to do this though, so figured I'd ask before filing a WebIDL syntax change. I see in lib/productions/type.js that the generic types seem to be special-cased and hard-coded, so I figure that I am out of luck for introducing new ones. I only really care about introducing a new "opaque" types. That is to say, I'd be perfectly satisfied with something like:
interface Something<T> { };
If not at the WebIDL level, I'd at least like to be able to add to the list of "known" parameterized types at the API level, something like:
I am just trying to do something like this:
I can't for the life of me figure out how to do this though, so figured I'd ask before filing a WebIDL syntax change. I see in
lib/productions/type.js
that the generic types seem to be special-cased and hard-coded, so I figure that I am out of luck for introducing new ones. I only really care about introducing a new "opaque" types. That is to say, I'd be perfectly satisfied with something like:If not at the WebIDL level, I'd at least like to be able to add to the list of "known" parameterized types at the API level, something like:
WebIDL.parse(string, { extraParameterizedTypes: "Something" });
And then have that added to the existing static list.
The text was updated successfully, but these errors were encountered: