Re: [WebIDL] Handling undefined in Overload Resolution Algorithm

On 7/19/11 1:06 PM, Jonas Sicking wrote:
> On Tue, Jul 19, 2011 at 6:04 AM, Lachlan Hunt<>  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 the proposal, yes.  This is already true if the nullable type is 
something like |String?|, but not if the nullable type is |Node|.  The 
proposal is to make is to passing |undefined| where an interface type is 
expected behaves the same as passing null (as opposed to throwing 
immediately because no overload is found).


Received on Tuesday, 19 July 2011 17:33:08 UTC