Is storing the same value to an object twice "modifying" it once or twice? :-)
-
-
-
Replying to @johnregehr
You're no fun. Do you have a citation for that though? Is "modifying" actually defined?
1 reply 0 retweets 0 likes -
Replying to @RichFelker
I am simply following the rule that the worst reasonable interpretation is probably the best one
1 reply 0 retweets 5 likes -
Replying to @johnregehr
I agree we probably have to interpret it that way, but...
1 reply 0 retweets 0 likes -
Replying to @RichFelker @johnregehr
It seems likely the motivation of the UB was ambiguity of which store happens first, which doesn't arise if both are the same value.
1 reply 0 retweets 0 likes -
Replying to @RichFelker
I agree with that motivation. but then there are modern compilers...
2 replies 0 retweets 0 likes -
Replying to @johnregehr
It's easy to see how the ambiguity could lead to real UB (not just unspecified order) with modern compilers when the values differ.
1 reply 0 retweets 0 likes
For example one code path might assume the first value was stored and the other assume the second, leading to ballooning contradictions.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.