Didn't sound that Java-specific to me: https://doc.rust-lang.org/std/collections/struct.HashMap.html https://doc.rust-lang.org/std/collections/struct.HashMap.h

Didn't sound that Java-specific to me: https://doc.rust-lang.org/std/collections/struct.HashMap.html https://doc.rust-lang.org/std/collections/struct.HashMap.htm... http://hackage.haskell.org/package/hashmap-1.3.3/docs/Data-HashMap.html http://hackage.haskell.org/package/hashmap-1.3.3/docs/Data-H... https://stdlib.ponylang.org/collections-HashMap/ https://stdlib.ponylang.org/collections-HashMap/ https://api.dartlang.org/stable/1.24.3/dart-collection/HashMap-class.html https://api.dartlang.org/stable/1.24.3/dart-collection/HashM... https://pocoproject.org/docs/Poco.HashMap.html https://pocoproject.org/docs/Poco.HashMap.html For me, HashMap is an abstract data type that adheres to the Map interface and is implemented with (i.e. has the performance characteristics of) a hash table. It's a subset of Map, hence the "go's maps are hashmaps" remark. HashSet is often implemented with hash tables too. I guess the difference is ADT vs data structure (and I see your point there), not Java-specificity.