- From: Domenic Denicola <notifications@github.com>
- Date: Wed, 29 Mar 2017 02:54:51 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <heycam/webidl/pull/286/review/29678176@github.com>
domenic commented on this pull request. > + <a href="#extended-attributes-applicable-to-types">applicable to types</a>. + 1. If |type| appears as part of a <emu-nt><a href="#prod-Type">Type</a></emu-nt> production + within an <emu-nt><a href="#prod-DictionaryMember">DictionaryMember</a></emu-nt> production, + add to |extended attributes| all of the [=extended attributes=] present in the production's + <emu-nt><a href="#prod-ExtendedAttributeList">ExtendedAttributeList</a></emu-nt> that are + <a href="#extended-attributes-applicable-to-types">applicable to types</a>. + 1. If |type| is a [=typedef=], add the [=extended attributes associated with=] the type being + given a new name to |extended attributes|. + 1. Return |extended attributes|. +</div> + +For any [=type=], the [=extended attributes associated with=] it must only contain +[=extended attributes=] that are +<a href="#extended-attributes-applicable-to-types">applicable to types</a>. + +The [=type name=] of a type associated with [=extended attributes=] is the concatenation of the OK, I can't add an example since it's actually impossible to use any of the current type-applicable extended attributes with nullable types, or use them together. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/heycam/webidl/pull/286#discussion_r108635994
Received on Wednesday, 29 March 2017 09:55:25 UTC