It's immutable by default, with mutation only when managed (most famously a Haskell thing). It has a rich type system with ADTs and generics but without subtyping (very much the ML/Haskell tradition). It distinguishes between validation-like failures and system-level errors, handling the former with values and the latter with panics (i.e. noncaught exceptions) - Erlang is the most famous example of this style, but it's common in Haskell and ML too. It tries to push functionality into libraries rather than the core language - it seems to care about having sensible, consistent semantics rather than ad-hoc.
It really depends on what you think are the features of Haskell that typify its "family". If you think it's typified by things like type inference, sum types, and typeclasses, then Rust will feel very Haskell-y, but if you think it's typified by higher kinded types, laziness, and functional purity, then it won't feel very Haskell-y at all.
Personally, I think Haskell and C++ are the two biggest influences I feel when using Rust: it has a lot of Haskell's philosophy around data types and polymorphism, and a lot of C++'s philosophy around the life cycle of resources, and the cost of abstractions.
Re:How to stop functional programming
by AnimalMuppet on Tuesday February 23, 2016 @03:41PM
(#11162145)
I think the life cycle of resources issue was a big reason why I was surprised to hear people say that Rust was Haskell-like.
Re:How to stop functional programming
by steveklabnik on Tuesday February 23, 2016 @02:08PM
(#11161433)
I'm in the "no" camp, personally, but we _did_ inherit a lot of things from OCaml. The initial compiler was written in it, a lot of the syntax and features are inspired by it, and it just _feels_ more ML than Haskell.
Rust may not be a functional language, but it draws heavy inspiration from them.
[Edit: I see that the link from jnbiche is probably going to answer my question, though it's going to take me a while to digest it...]