News for hackers. Stuff that matters.
Re:Rust 1.0: Scheduling the trains by XorNot on Friday December 12, 2014 @06:53PM (#8743411)
So something that always holds me up with new languages: workflow.

What's a Rust development workflow look like at the moment, from editor, to reference materials, to debugging? I tend to be an IDE person (which obviously doesn't and won't exist for some time) so I'm pretty eager to hear how other people have been doing it.

Re:Rust 1.0: Scheduling the trains by thristian on Friday December 12, 2014 @10:51PM (#8744059)
I've only dabbled in Rust, but my setup for writing Rust in Vim is pretty similar to my setup for writing anything else: vim on one side of the screen, where I do my editing and type ":make" to try and build it (with Vim's makeprg configured to run "cargo test"). On the other side, a browser open to the Rust stdlib docs, and a terminal for interactive testing.