- From: peria <notifications@github.com>
- Date: Fri, 07 Jun 2019 01:37:25 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 7 June 2019 08:37:51 UTC
Now we define [**number of nullable member types**](https://heycam.github.io/webidl/#dfn-number-of-nullable-member-types) in union types, and [**includes a nullable type**](https://heycam.github.io/webidl/#dfn-includes-a-nullable-type) in general types. Currently, **number of nullable member types** is practically referred in the definition of **includes a nullable type**. IIUC, "a union type `A` includes a nullable type" means "`A`'s number of nullable member types is 1". So what I wonder is if we need to define **number of nullable member types**. As I describe above, it's quite similar to **includes a nullable type**, and **includes a nullable type** does not require **number of nullable member types** in its definition. A small difference in their definition seems **includes a nullable type** assumes annotated types whose inner type is nullable. -- 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/issues/735
Received on Friday, 7 June 2019 08:37:51 UTC