Two years of Rust

Re:Two years of Rust by coldtea on Monday May 15, 2017 @05:13PM (#14345175)

>about how futures-based concurrency spreads into your code through huge amounts of necessary boilerplate (`.and_then(...).and_then(...).and_then(...)`)

How is that more boilerplate than any other way to have concurrency?

[ Parent | on HN ]

Re:Two years of Rust by steveklabnik on Monday May 15, 2017 @05:14PM (#14345184)

Async/await is commonly suggested as a lighter-weight syntax.

[ Parent | on HN ]

Re:Two years of Rust by coldtea on Tuesday May 16, 2017 @02:21AM (#14347736)

Well, isn't async/await complementary to futures?

[ Parent | on HN ]

Re:Two years of Rust by xorxornop on Tuesday May 16, 2017 @03:41AM (#14347990)

Oh, it is, it just makes them a lot easier to use. The compiler does method restructuring magic behind the scenes to build the necessary state machines. Everything gets a lot easier to understand.

[ Parent | on HN ]

Re:Two years of Rust by arianvanp on Monday May 15, 2017 @05:18PM (#14345205)

Do notation makes this stuff a whole lot more readable (See Haskell). Or Async-await (See C#)

[ Parent | on HN ]

Re:Two years of Rust by marcosdumay on Monday May 15, 2017 @05:57PM (#14345503)

About do notation, can't Rust get something similar with macros? (I still didn't get to making macros in it.)

[ Parent | on HN ]

Re:Two years of Rust by steveklabnik on Monday May 15, 2017 @06:33PM (#14345757)

There is a crate that does it in a duck-typed manner. It's not clear that the stronger typed version can work. We'll see.

[ Parent | on HN ]

Re:Two years of Rust by brandur on Monday May 15, 2017 @05:40PM (#14345375)

+1. Also, Go's goroutines and channels.

[ Parent | on HN ]