Support for Optional members in interfaces followed by non-optional ones

[fafalone]

tB applies this language restriction to interfaces as well as normal subs/functions; I'm not sure if it's possible for the latter, but for interfaces, there's currently a lot of interfaces where I'm having to drop 'optional' attributes so the COM spec clearly supports this... how practical would it be to support this in tB and is it something that should be added?

I'd say it should be added because it aids in clarity, not having to create and pass empty parameters that might be interpreted as 0.

[mburns08109]

(quoting @WaynePhillipsEA on Discord)
WaynePhillipsEA — Today at 4:08 PM
Ahem... you might want to try passing a pointer value to byref-UDTs in tB ;). It's an undocumented, but perhaps rather useful, feature. Though note that we may later refine the "feature".
[4:09 PM]
I'm particular, I find it comes in very handy when working with union types.
(/quoting @WaynePhillipsEA on Discord)