@TimSweeneyEpic Read your old slides. Thinking about 100-core problem. Your thoughts on Rust for UE in ~5-20 years? http://www.iiswc.org/iiswc2008/sildes/keynote_1.pdf …
-
-
Replying to @nathanstocks
I'll need to dig into Rust and think about this.
1 reply 0 retweets 0 likes -
Replying to @TimSweeneyEpic
Maybe solves the hardest parts. Safe, lock-free shared memory via compile-time data ownership checks. Watching with interest
1 reply 0 retweets 0 likes -
Replying to @nathanstocks
Ok, I think message passing concurrency is too limited and manual for complex code, e.g. updating actors in a game engine.
2 replies 0 retweets 0 likes -
Replying to @TimSweeneyEpic @nathanstocks
I think that transactions (in the context of unbounded transactional memory updates) are the desirable solution.
1 reply 0 retweets 0 likes
Replying to @TimSweeneyEpic @nathanstocks
Until we have that, I think C++ will continue to win for multithreaded client software. It's unsafe, but fast and powerful.
2:30 PM - 27 Dec 2016
0 replies
0 retweets
0 likes
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.