-
Notifications
You must be signed in to change notification settings - Fork 159
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
Interaction of extended attributes and typedefs is weird #649
Comments
Also, is this allowed?
https://heycam.github.io/webidl/#idl-typedefs says no extended attributes apply to typedefs, but presumably that means the actual typedef statement, right? So in this case, does the arg get clamping behavior? |
Dang, I'd hoped given that one of the points in my OP of #286 was about interaction with typedefs, that we'd nailed this the first time around. OK, let me try to reload this into my brain...
It seems like it should be an integer type. Simpler, it seems to me that given
Right, that was definitely the intent there. I guess it should instead say something like
It seems like it should, right? The typedef should be transparent, ideally. https://heycam.github.io/webidl/#idl-type-extended-attribute-associated-with seems to do the right thing, so I guess this is just about whether |
That would be ideal; it just doesn't seem to be what the spec says right now.
I agree.
Hmm. Yes, I think so... |
Consider this IDL:
Is this valid IDL? Per https://heycam.github.io/webidl/#idl-type-extended-attribute-associated-with step 6, the extended attributes "associated with"
ClampedLong
include[Clamp]
. But https://heycam.github.io/webidl/#Clamp says:and
ClampedLong
is not an "integer type" in the sense linked here, as far as I can tell...Presumably the intent is to allow this, right? That should be made clearer.
The text was updated successfully, but these errors were encountered: