On 6 Sep 2017, at 10:28, T L <tapir....@gmail.com> wrote:
> It is just weird that the evaluation timing of *p is different to other
> expressions, such as, *p+0, *p*1, func()int{return *p}m etc.
The value depends on a data race so it's entirely undefined in all cases. That
the actual outcome then depends on trivial differences that may affect CPU
loads/stores, instruction ordering, register usage, etc isn't surprising.
//jb
--
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.
For more options, visit https://groups.google.com/d/optout.
