Benefits of named return values in Go

Re:Benefits of named return values in Go by heythere124 on Friday June 30, 2017 @08:25AM (#14670263)

Your "solution" is possible in many languages. It's just to give threads complete ownership of data they use. It doesn't require a special type system.

In general I don't think Rust actually adds much abstraction that isn't already in say Python. What it does is enforce tight constraints.

[ Parent | on HN ]

Re:Benefits of named return values in Go by Filligree on Friday June 30, 2017 @09:19AM (#14670496)

The constraints are important. They're what let you code safely, and also give the compiler the ability to optimize better.

[ Parent | on HN ]

Re:Benefits of named return values in Go by heythere124 on Friday June 30, 2017 @10:09AM (#14670806)

Not sure those optimisations are worth much. And it's only safety by forcing lowest common denominator code and making you justify everything to a dumb compiler. Rust serves a niche, but it is a tight niche IMO.

[ Parent | on HN ]

Re:Benefits of named return values in Go by pcwalton on Friday June 30, 2017 @12:44PM (#14671889)

Aliasing info is hugely important in optimization. In fact, it's needed to solve this very bug.

Aliasing info is, fundamentally, what allows Rust to have memory safety without GC.

[ Parent | on HN ]