cmrx64

58 ms·

661.
by cmrx64 13y ago
The guides are up-to-date and maintained, but the tutorial itself is long, bulky, and ill-maintained. There is a contractor working on rewriting it.
662.
by cmrx64 13y ago
We will follow http://semver.org/
663.
This Week in Rust(cmr.github.io)
5 points by cmrx64 13y ago|0 comments
664.
by cmrx64 13y ago
Hi! I picked this theme indeed because I thought it looked the best on my screen. Would using a heavier font help? Or maybe just setting the font color to true black?
665.
by cmrx64 13y ago
It is Sender and Receiver now. TX and RX aren't obvious to non-English-speakers
666.
This Week in Rust(cmr.github.io)
68 points by cmrx64 13y ago|21 comments
667.
This Week in Rust(cmr.github.io)
91 points by cmrx64 13y ago|69 comments
668.
This Week in Rust(cmr.github.io)
70 points by cmrx64 13y ago|27 comments
669.
by cmrx64 13y ago
Precisely.
670.
by cmrx64 13y ago
Before the end of 2014.
671.
by cmrx64 13y ago
On the contrary, this decision was solely motivated by the desire to reduce fragmentation. The interfaces libstd provides can work under almost any runtime, and (mostly, but definitely in safe code) don't leak implementation details.
672.
This Week in Rust(cmr.github.io)
2 points by cmrx64 13y ago|0 comments
673.
by cmrx64 13y ago
Indeed, we mark them as readonly/readnone when we can.
674.
This Week in Rust - LTO, dead code lint, and more(cmr.github.io)
3 points by cmrx64 13y ago|0 comments
675.
This Week in Rust – Static linking, Win64(cmr.github.io)
57 points by cmrx64 13y ago|23 comments
676.
Ask HN: What do you expect in a language's 1.0 release?
8 points by cmrx64 13y ago|3 comments
677.
by cmrx64 13y ago
I'll see what I can do
678.
by cmrx64 13y ago
What would you want to see in such a tutorial? A lot goes into even the most barebones functional operating systems.
679.
by cmrx64 13y ago
No problem! I know how hard it can be tracking the fast-moving Rust.
680.
The State of Rust 0.8(cmr.github.io)
8 points by cmrx64 13y ago|0 comments
681.
by cmrx64 13y ago
Well, yes, borrowed pointers can point onto the stack, but we don't have string values that can live on the stack, not really. String slices, denoted as `&str`, can point into the stack if you construct them from a `[u8, ..N]` (a f
682.
by cmrx64 13y ago
Rust doesn't have stack allocated strings, I have no idea what you're talking about. We have string slices , but there's no way to stack allocate those, they don't own their allocation.
683.
by cmrx64 13y ago
But one can implement those, they are language items.
684.
by cmrx64 13y ago
Besides, rustc already does an impressive amount of linting.
685.
by cmrx64 13y ago
thanks, but Seldaek (Jordi) has been doing all the stuff with the frontend, which is where most of praise deserves to go IMO
686.
by cmrx64 13y ago
It's still pre-alpha, don't use it if you don't want to be dealing with daily backwards-incompatible changes (mostly in the libraries), occasional language features being modified or removed, etc. I think by 0.8 or 0.9 the la
687.
Rust's new documentation generator: 95% done(mail.mozilla.org)
80 points by cmrx64 13y ago|28 comments
688.
by cmrx64 13y ago
Been watching floobits since you announced it. Very excited to see it launch with bunches of new features!
689.
by cmrx64 13y ago
(we actually do support MIPS)
690.
by cmrx64 13y ago
Hi! I'm working on the new rustdoc (the current one is horribly outdated and all-around crappy). Any other feature requests? I'm tracking them at https://github.com/mozilla/rust/wiki/Bikeshed-rustdoc

More ›