2 ms·
Yeah - I figured it would be related to interopt with the Java runtime. However it is a bit sad, language designers never seem to bother cleaning up collection
by throwaway4good 6y ago
Yeah - I figured it would be related to interopt with the Java runtime.
However it is a bit sad, language designers never seem to bother cleaning up collection types when designing a new language.
There really should be just one list type.
- dvdkon 6y agoAgree with array/list, we don't need more contiguous chunks of memory, but tuples are very different, if only because they allow elements of different types. They're really more ad-hoc unnamed structs than collections.
- nalenth 6y agoin strictly typed languages that would be correct, and I still somewhat agree, but AviatorScript is dynamically typed, and allows lists containing elements with different types. It's basically List<Object>. So it seems to be a strictly semantic distinction.