W3C home > Mailing lists > Public > public-media-capture@w3.org > February 2016

Re: Using enums to avoid default true in "settings dictionaries" (#466, #467, #471)

From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 19 Feb 2016 23:36:36 -0800
Message-ID: <CAJrXDUFw90WMxRe2s51mpXtaSocs8tc2ujfdVyv5YhU5JwLN=g@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Jan-Ivar Bruaroey <jib@mozilla.com>, Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On Fri, Feb 19, 2016 at 10:50 PM, Martin Thomson <martin.thomson@gmail.com>

> On 19 February 2016 at 21:50, Peter Thatcher <pthatcher@google.com> wrote:
> > But how does converting to an enum help at all?   Wouldn't undefined then
> > just get turned into an enum value, which is truthy?
> An enum ensures that all valid values that are equally truthy, so
> truthy/falsy becomes irrelevant.  Yes, the default is truthy, but so
> is every valid value.
So pc.createDataChannel("label", {ordered: undefined}) is still going to be
ordered, right?

So how are we better off with an enum in this case?

> > And if a truthy value of a default is discouraged, then are the only
> > encouraged defaults the falsy ones (false/null/""/0/NaN)?
> This is only relevant for dictionary parameters with Boolean types.
Received on Saturday, 20 February 2016 07:37:46 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 20 February 2016 07:37:46 UTC