За map-овете не се наблегна на това, кой са comparable типове, и че само те могат да бъдат ключове в map (на лекциите по Python, Ruby доста го повтарят а при нас нито миналата, нито днешната).
Но си отворих Key types и беше обяснено хубаво, върнах се в лекцията и всичко си го имаше (линка със спесификацията ми беше малко мътен).
Не беше споменато за iteration order-a :
Since Go 1 the runtime randomizes map iteration order, as programmers relied on the stable iteration order
of the previous implementation. If you require a stable iteration order you must maintain a separate data
structure that specifies that order.
За конкуренцията и map-овете ми хареса това обяснение:
Why are map operations not defined to be atomic?
After long discussion it was decided that the typical use of maps did not require safe access from multiple
goroutines,and in those cases where it did, the map was probably part of some larger data structure or computation
that was already synchronized. Therefore requiring that all map operations grab a mutex would slow down most programs
and add safety to few. This was not an easy decision, however, since it means uncontrolled map access can
crash the program.
The language does not preclude atomic map updates. When required, such as when hosting an untrusted program,
the implementation could interlock map access.
Просто исках да наблегна, какво за мен е важно.
