On Tue, Jul 19, 2011 at 6:04 AM, Lachlan Hunt <lachlan.hunt@lachy.id.au> wrote: > Hi, > Refer to discussion in a Mozilla bug 648722 [1]. > > When undefined in passed to an overloaded function, the overload resolution > algorithm should not exclude nullable non-primitive types. I'm not quite sure I understand what you are suggestion. Are you saying that we should treat undefined as null when calling a function that takes a nullable type? / JonasReceived on Tuesday, 19 July 2011 17:07:14 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:04 UTC