Axel Rauschmayer wrote:
The thought is this: If you use [] to access members of a collection (array, map, etc.) then you’d still have the .@ operator to access properties via computed names. Long-term, .@ would become the recommended way of doing this.
The last sentence does not follow, even if we make obj.@privateName and obj.@stringName both work.
I'm not (just) saying we should not aspire to such a long-term migration to obj.@name over obj[name]. (I think that we shouldn't want that, btw, but it is not my point.)
I'm saying there is too much history and inertia to believe that just because you can do obj.@anyName, people will move their code to do that, or write all new code some years hence when old browsers have retired that uses only obj.@anyName.
/be _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
