On 1/23/23, Peter Rabbitson <ribasu...@gmail.com> wrote: ... > I guess I will spend some time to learn how to poke around the generated > assembly tomorrow...
If I understand correctly you are trying to force your model of the world into the Go memory model. The models are different, so this won't work. Please also note that your model of current execution complexes is probably valid today, but it could change anytime. The Go memory model is differently restricting to accommodate for that future. Of course you can implement what you want using any tool available, but the correct execution can't be ensured by the Go memory model if you don't build on that. -- 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/CA%2BctqrpxFc0htmyO3ApMtLWMKdyig-Eoay0x%2BnU1sO8Lmmw2hA%40mail.gmail.com.
