News for hackers. Stuff that matters.
Re:The Path to Rust by kibwen on Thursday May 26, 2016 @02:11AM (#11775927)
I'm unsure what this is implying. Rust is fully capable of handling signals, it just doesn't provide any nice APIs for such in the standard library.
Re:The Path to Rust by SiVal on Thursday May 26, 2016 @06:05AM (#11776799)
Is there a roadmap for what is currently planned for the standard library? A lot of language choice these days comes down to what high-quality batteries are included and what will require either trusting some unknown 3rd party's github project or your own homemade version.
Re:The Path to Rust by Gankro on Thursday May 26, 2016 @09:11AM (#11777603)
The first-party stuff in the pipeline is basically: https://github.com/rust-lang-nursery

Off the top of my head, Time and SIMD are the only two first-party efforts that are missing from there.

Things which will, at this rate, probably never be added -- either because there isn't a "standard" solution to these problems or because it doesn't seem worth it:

* async io

* web framework/http

* numerical hierarchies and bignums

* linear algebra / stats

* GUIs

* "human" time / calendars

Re:The Path to Rust by kibwen on Thursday May 26, 2016 @11:42AM (#11778810)
Eh, considering that TCP support already exists in the standard library, I could see HTTP also being added someday if there were sufficient demand.

Bignums in general are a bit too open-ended, but I could see bigints at least being added someday.

And as for async io, I think it's the same story as with HTTP: imaginably included contingent on implementation maturity and user demand.