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
Rather than expecting each bindings language to come up with a generic naming scheme to handle unions, I think we should put the onus on WIT authors to select reasonable case names on an equivalent variant.
A quick Github search (and review of WASI) suggests that unions are not currently in use outside of tests and samples.
I'd be fine dropping them too. Initially they were added because the proposal spawned out of Web IDL, which has union. But yeah, I can see how it ends up being a special case for many languages, especially the statically-typed ones.
Even in JavaScript, they're still tagged awkwardly and don't actually correspond to the IDL / TypeScript equivalents, so this seems fine to me as well.
Activity
alexcrichton commentedon Aug 21, 2023
Personally I'd agree with this and would be in favor 👍
lukewagner commentedon Aug 21, 2023
I'd be fine dropping them too. Initially they were added because the proposal spawned out of Web IDL, which has
union. But yeah, I can see how it ends up being a special case for many languages, especially the statically-typed ones.guybedford commentedon Aug 21, 2023
Even in JavaScript, they're still tagged awkwardly and don't actually correspond to the IDL / TypeScript equivalents, so this seems fine to me as well.