- From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Date: Tue, 19 Jul 2011 20:58:28 +0200
- To: Jonas Sicking <jonas@sicking.cc>
- CC: public-script-coord@w3.org
On 2011-07-19 19:06, Jonas Sicking wrote: > 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? That's what the algorithm already says when the parameter is a nullable primitive type. I don't really have a strong opinion either way, the point is just to make all nullable types consistent when undefined is passed. -- Lachlan Hunt - Opera Software http://lachy.id.au/ http://www.opera.com/
Received on Tuesday, 19 July 2011 18:59:02 UTC