On Sun, Sep 8, 2019 at 1:24 PM Michael Luder-Rosefield < [email protected]> wrote:
> I'd suggest that the best way of doing this, without breaking existing > code, is to put some sugar around Maps so that they can be used in a more > Object-y way. For starters, Map literal declarations and assignment could > benefit from this. > > or Just use a WeakMap > Suggestions for syntax welcome! > > On Sun, 8 Sep 2019, 12:36 Tadas Lapė, <[email protected]> wrote: > >> The problem >> >> Javascript allows to index objects not only with strings, numbers, but >> also with objects. It uses toString() object method to calculate the object >> index. If method is not overwritten, the generated index is "[object >> Object]". Many users do not know this or forget this and cause different >> objects going into same index when using more of them. >> >> The solution >> >> Instead of using the default value "[object Object]" for objects, use >> their hash codes. You can also prepend them with "function:" or "object:" >> to let the user know index origin when iterating over object keys. And if >> person has overwritten the behavior of toString() object method, use it's >> returned value as index (to consider). This should be less error-prone. >> _______________________________________________ >> es-discuss mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/es-discuss >> > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
