6 ms·

I’m waiting for async/await... that will start the party!

steveklabnik 8y ago
You and many others... the lang team has been hard at work. We want it to ship, but we also want to get it right. It will be a huge deal, for sure.
- parley 8y ago
  I'm waiting eagerly too, thanks for all the hard work you do! I read somewhere in all the discussions that Carl was hesitant to go all-in on futures 0.3 (those are definitely landing in std, right?) in tokio before some additional ergonomics had landed, possibly some language feature among them but I may misremember... Do you know the list of things and possibly their tracking issues? Futures in std, async/await, etc, something something more? Would love to be able to keep track and follow along :)
  - steveklabnik 8y ago
    No problem, though I don't work on this aspect at all, to be clear :) > (those are definitely landing in std, right?) Yes. > Do you know the list of things and possibly their tracking issues? https://areweasyncyet.rs/ https://areweasyncyet.rs/ :D
    - parley 8y ago
      Ha, that was a superb answer, thanks! :D I'll be checking that site! I know you may not have your fingers in this particular flower pot, so the "you" was directed at the entire Rust community. However, while we're here you still get a big personal thanks -- your Rust for Rubyists got me hooked those years back and the docs/book (1st ed and then 2nd ed with Carol) work you've done since is nothing short of amazing -- and with these latest developments I hope you find a great place to continue your work <3
- mamcx 8y ago
  Asynchronous/await is also the reason to delay generators?
  - steveklabnik 8y ago
    In a sense; generators are currently an implementation detail of async/await. The plan is to get async/await shipped first, and then stabilize generators afterward.
- SlowRobotAhead 8y ago
  Cool, then serious movement on embedded please!
  - steveklabnik 8y ago
    That's happening totally concurrently! We've already made big strides this year, and I'm expecting more good stuff this year. There's even a new, embedded focused conference!
    - SlowRobotAhead 8y ago
      Please consider approaching Segger. If a real IDE supports Rust compiler and builds in real debug, more than just some hobbiest weirdos (heh) will be able to consider it.
      - majewsky 8y ago
        Besides inflammatory language not being appropriate (here or anywhere else, really), what makes you think that only "hobbyist weirdos" are using Rust? When I look at "This Week in Rust", it lists job openings for Rust developers every week, so we're way past the "bunch of enthusiast" stage.
        SlowRobotAhead 8y ago
        I don’t know how to comfort someone that thinks a light hearted “hobbiest wierdos (heh)” is offensive and inflammatory. Show me serious embedded device mfgs using Rust. Actually using. Not some testimonial on the Rust site. The real truth is no company is going to use it until there is serious use will happen until there is IDE support. Segger is a company large enough to be taken serious and unlike Keil or IAR small enough to get it done. Great things start with hobbiest wierdos. IMO... once you stop looking for things to be offended by you can get to work, son.
pas 8y ago
https://boats.gitlab.io/blog/post/romio/ https://boats.gitlab.io/blog/post/romio/ you can start playing with it right now
hinkley 8y ago
If my experience with Node is any indication, you want to be fashionably late to this party. It takes a while for modules to adapt to such a big change, and the modules you are most interested in may have dependencies on those modules. It takes a bit of time for concurrency changes to percolate up the dependency graph.
- qaq 8y ago
  ? if a function returns a promise you are good and you can promisify cb style libs so how was this an issue?
  - jabl 8y ago
    Perhaps, with the absence of an officially sanctioned, easy-to-use async story, people resort to stuff like thread-per-connection. Like rocket.rs. When said async stuff appears in the core language, it will still take time for other code to be rewritten.

You and many others... the lang team has been hard at work. We want it to ship, but we also want to get it right. It will be a huge deal, for sure.

parley 8y ago
I'm waiting eagerly too, thanks for all the hard work you do! I read somewhere in all the discussions that Carl was hesitant to go all-in on futures 0.3 (those are definitely landing in std, right?) in tokio before some additional ergonomics had landed, possibly some language feature among them but I may misremember... Do you know the list of things and possibly their tracking issues? Futures in std, async/await, etc, something something more? Would love to be able to keep track and follow along :)
- steveklabnik 8y ago
  No problem, though I don't work on this aspect at all, to be clear :) > (those are definitely landing in std, right?) Yes. > Do you know the list of things and possibly their tracking issues? https://areweasyncyet.rs/ https://areweasyncyet.rs/ :D
  - parley 8y ago
    Ha, that was a superb answer, thanks! :D I'll be checking that site! I know you may not have your fingers in this particular flower pot, so the "you" was directed at the entire Rust community. However, while we're here you still get a big personal thanks -- your Rust for Rubyists got me hooked those years back and the docs/book (1st ed and then 2nd ed with Carol) work you've done since is nothing short of amazing -- and with these latest developments I hope you find a great place to continue your work <3
mamcx 8y ago
Asynchronous/await is also the reason to delay generators?
- steveklabnik 8y ago
  In a sense; generators are currently an implementation detail of async/await. The plan is to get async/await shipped first, and then stabilize generators afterward.
SlowRobotAhead 8y ago
Cool, then serious movement on embedded please!
- steveklabnik 8y ago
  That's happening totally concurrently! We've already made big strides this year, and I'm expecting more good stuff this year. There's even a new, embedded focused conference!
  - SlowRobotAhead 8y ago
    Please consider approaching Segger. If a real IDE supports Rust compiler and builds in real debug, more than just some hobbiest weirdos (heh) will be able to consider it.
    - majewsky 8y ago
      Besides inflammatory language not being appropriate (here or anywhere else, really), what makes you think that only "hobbyist weirdos" are using Rust? When I look at "This Week in Rust", it lists job openings for Rust developers every week, so we're way past the "bunch of enthusiast" stage.
      - SlowRobotAhead 8y ago
        I don’t know how to comfort someone that thinks a light hearted “hobbiest wierdos (heh)” is offensive and inflammatory. Show me serious embedded device mfgs using Rust. Actually using. Not some testimonial on the Rust site. The real truth is no company is going to use it until there is serious use will happen until there is IDE support. Segger is a company large enough to be taken serious and unlike Keil or IAR small enough to get it done. Great things start with hobbiest wierdos. IMO... once you stop looking for things to be offended by you can get to work, son.

pas 8y ago

https://boats.gitlab.io/blog/post/romio/ https://boats.gitlab.io/blog/post/romio/ you can start playing with it right now

hinkley 8y ago

If my experience with Node is any indication, you want to be fashionably late to this party. It takes a while for modules to adapt to such a big change, and the modules you are most interested in may have dependencies on those modules. It takes a bit of time for concurrency changes to percolate up the dependency graph.

qaq 8y ago
? if a function returns a promise you are good and you can promisify cb style libs so how was this an issue?
- jabl 8y ago
  Perhaps, with the absence of an officially sanctioned, easy-to-use async story, people resort to stuff like thread-per-connection. Like rocket.rs. When said async stuff appears in the core language, it will still take time for other code to be rewritten.