First keynote announcement for #RustNow2017... I mean #CppNow2017! http://cppnow.org/2017-conference/announcements/2017/03/15/rust-keynote.html … @nikomatsakis @rustlang @cppnow
-
-
Replying to @blelbach @nikomatsakis and
my biggest problem with this is that the only Q I could ask for this keynote is VERY inflammatory.
1 reply 0 retweets 1 like -
(namely "how do I write an API for atomics that I can have truly immutable references to".)
2 replies 0 retweets 0 likes -
not sure I understand. Rust has support for lock-free DS eg https://aturon.github.io/blog/2015/08/27/epoch/ …
1 reply 0 retweets 1 like -
Atomic::store takes &self and not &mut self. Which means I can't have a reference to [1/?]
1 reply 0 retweets 0 likes -
an Atomic that is truly immutable, since you can store to `&`. This in turn means [2/?]
1 reply 0 retweets 0 likes -
that it's impossible to pass around a const view of the atomic, which for me is a [3/?]
1 reply 0 retweets 0 likes -
deal breaker when I'm doing bare metal code.
1 reply 0 retweets 0 likes
could use wrapper/newtype for a readonly/const view; but let's talk @ cppnow, since I don't find twitter conducive to technical back-n-forth
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.