neo-one
neo-one copied to clipboard
Consider trying to re-implement JS semantics for objects as key values in things like maps and sets in compiler
Until recently we supported JS semantics for when using an object/array as a key in a map and entry in a set. The same object assigned to two different variables would correctly be considered two different keys in a map. But after needing to serialize these structs in the compiler so that they were primitive stack item types as keys we lost that JS semantic. Now if two identical objects from different locations are set in a map the map will use the latest one.