Forgot to retitle it.
On Jan 3, 2015 9:44 PM, "Isiah Meadows" <impinball at gmail.com> wrote:

> > From: Axel Rauschmayer <axel at rauschma.de>
> > To: brendan at mozilla.org
> > Cc: es-discuss list <es-discuss at mozilla.org>
> > Date: Sun, 4 Jan 2015 03:17:54 +0100
> > Subject: Re: Implicit coercion of Symbols
> > Does it have to be a Reflect.* method? It could be
> `Symbol.prototype.getDescription()` or a getter.
> >
> >> On 04 Jan 2015, at 02:25, Brendan Eich <brendan at mozilla.org> wrote:
> >>
> >> Rick Waldron wrote:
> >>>
> >>> That example above is pretty compelling for throw always consistency.
> >>
> >>
> >> With a new Reflect.* API for converting a symbol to its
> diagnostic/debugging string?
> >>
> >> If you agree, please file a bugs.ecmascript.org ticket.
> >>
> >> /be
> >> _______________________________________________
> >> es-discuss mailing list
> >> es-discuss at mozilla.org
> >> https://mail.mozilla.org/listinfo/es-discuss
> >
> >
> > --
> > Dr. Axel Rauschmayer
> > axel at rauschma.de
> > rauschma.de
>
> A good name for such a getter would be, IMO,
> `Symbol.prototype.description`. It would also seem to fit with some other
> common JS idioms, such as `Array.prototype.length`, etc. It also feels
> clearer and cleaner as a getter than an instance method or function.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150104/08b9c0a3/attachment.html>

A good name for such a getter would be, IMO,
`Symbol.prototype.description`. It would also seem to fit with some other
common JS idioms, such as `Array.prototype.length`, etc. It also feels
clearer and cleaner as a getter than an instance method or function.