That issue is so popular that the Go designers are planning changes to the language:
https://github.com/golang/go/discussions/56010
Just do a nt := newTask() inside the loop and omit the declaration in line 83.
Does that solve your issue?
Louis on Nostr: npub1s2kql…p8cla You fell into the popular Go trap, in that you essentially assign ...
npub1s2kql4vgtz3ekvh70qsvwc0yykws4cuxtd09ha0z0kx7ufpg0fkqhp8cla (npub1s2k…8cla) You fell into the popular Go trap, in that you essentially assign only the last of the newTask assignments into your map, so all tasks are effectively the same one task.
That issue is so popular that the Go designers are planning changes to the language:
https://github.com/golang/go/discussions/56010
Just do a nt := newTask() inside the loop and omit the declaration in line 83.
Does that solve your issue?
That issue is so popular that the Go designers are planning changes to the language:
https://github.com/golang/go/discussions/56010
Just do a nt := newTask() inside the loop and omit the declaration in line 83.
Does that solve your issue?