On Fri, Jun 2, 2023 at 4:59 AM fliter <imc...@gmail.com> wrote: > > Map and slice are also concurrency-unsafe data structures. Why is map > designed to throw a fatal that cannot be recovered when there is a > concurrency conflict, but slice does not have any prompt? Are there any > design considerations?
Because some cases are easy and cheap to detect for maps, but there are no cases that are easy or cheap to detect for slices. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcX0F%3Df%2BYbM6NuJvK4dAkHvFE-CGnMP3T0276XjXH0Ow5A%40mail.gmail.com.