Re: [WebIDL] Handling undefined in Overload Resolution Algorithm

• From: Jonas Sicking <jonas@sicking.cc>
• Date: Tue, 19 Jul 2011 10:06:14 -0700
• To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
• Cc: public-script-coord@w3.org
• Message-ID: <CA+c2ei8=GYay5wzxYzBGF5cUbK5EJvx6s4CySjp79Hw4Ym650g@mail.gmail.com>

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?

/ Jonas

Received on Tuesday, 19 July 2011 17:07:14 UTC