unique string (uuid or otherwise) suffer same problem if generated in 2 different realm unaware of each other.
In any case, as mentioned before, this is very similar to instanceof or isPrototypeOf/getPrototypeOf and I don't see many concrete real cases problems except being able to serialize and deserialize @symbols in a unique way across realms (symbol name within a specific module scope mapped as unique or anything that could work I cannot think about now ^_^) Regards On Wed, Jul 31, 2013 at 10:16 AM, Kevin Smith <[email protected]> wrote: > >> To avoid accidental collision on the interned symbols, you must avoid >> accidental collision on the strings used as keys in this registration >> table. This demands exactly as much collision resistant of string choices >> as using the strings directly. And therefore also demands strings which are >> just as ugly. >> >> > I agree. A unique string to symbol registry would be a useless > indirection, as there is no information or ability stored in the symbol > that is not already inherent in the string used to fetch the symbol. > > The solution to your version+realm problem of this post is trivial with > string names. Just use a well-known unique string (uuid or otherwise). > > { Kevin } > > > _______________________________________________ > 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
