The Microsoft response to D and Rust: M# #RustLang http://lambda-the-ultimate.org/node/4862
-
-
Replying to @JohnBFair
@JohnBFair cool, but it doesn't look like it meets # 3 from this arbitrary wish list that interested me in#rustlang: http://sebastiansylvan.com/2013/05/25/language-design-deal-breakers/ …2 replies 2 retweets 0 likes -
Replying to @feslerj
@feslerj@JohnBFair it may also be interesting to note that here they've kept the pre/post-conditions which Rust tried and abandoned1 reply 1 retweet 0 likes -
Replying to @killerswan
.
@feslerj@JohnBFair I'm also far less excited than I used to be about languages that want programmers to do their own GC2 replies 0 retweets 1 like -
Replying to @killerswan
@killerswan@feslerj I'm certainly more wary of them in my old(er) age than I used to be.1 reply 1 retweet 0 likes -
Replying to @JohnBFair
@JohnBFair@killerswan#rustlang allows the GC ur thinking of, u just don't get the perf, is M# supposed to give u the perf and the GC?1 reply 1 retweet 0 likes -
Replying to @feslerj
@feslerj@JohnBFair I cannot speak about M# beyond that blog post, but currently Rust requires tons of cruft around lifetimes and borrowing2 replies 1 retweet 0 likes
@killerswan @feslerj @johnbfair Well, keep in mind that lifetimes/borrowing are also what allow shared memory without races. Not just GC.
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.