@nothings @jwatte @thorduragust Yes, I feel like people are conflating the _semantic_ difference with the _practical_ difference.
-
-
Replying to @cmuratori
@cmuratori@nothings@jwatte@thorduragust There is only a _semantic_ difference as far as I know - the actual codegen does not change.4 replies 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@nothings@thorduragust Turns out, if you follow the intended semantics, the programming language helps you.1 reply 0 retweets 0 likes -
Replying to @jwatte
@jwatte@nothings@thorduragust No it doesn't? Either you had a pointer at some point, which means you *'d it to turn it into a reference,1 reply 0 retweets 1 like -
Replying to @cmuratori
@cmuratori@jwatte@nothings@thorduragust or you didn't, and so you couldn't have had the bug. It's the same risk as pointers either way?1 reply 0 retweets 2 likes -
Replying to @cmuratori
@cmuratori@jwatte@nothings@thorduragust I've never understood the (specious, in my opinion) claim that references help here.4 replies 0 retweets 2 likes -
Replying to @cmuratori
@cmuratori@jwatte@nothings@thorduragust references prevent NULL pointers about as well as const prevents mutation.5 replies 1 retweet 9 likes -
Replying to @ianh_
@ianh_@cmuratori@jwatte@nothings@thorduragust But don't both trigger some compiler optimisations based on those assumptions?1 reply 0 retweets 0 likes -
Replying to @nicuveo
@nicuveo@ianh_@cmuratori@jwatte@nothings@thorduragust almost never, because the compiler unaware of the true origin of the c-p or ref.1 reply 0 retweets 0 likes -
Replying to @ezystory
@nicuveo@ianh_@cmuratori@jwatte@nothings@thorduragust e.g. Rust does this right, because it tracks lifetimes of ptr kinds.1 reply 0 retweets 0 likes
-
-
Replying to @cmuratori
@cmuratori@ezystory@nicuveo@ianh_@jwatte@nothings@thorduragust It is almost entirely a semantic construct as well.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@nicuveo@ianh_@jwatte@nothings@thorduragust Rust is giving llvm alias/mut constraints that C.. can't see. :-)0 replies 0 retweets 0 likes
End of conversation
New conversation -
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.