Have you looked at Rust? It uses Option types, has generics, also uses return values for error handling but has a lot more syntactic sugar to make it cleaner than in Go.
There are a number of RFCs in the pipeline to help with lifetimes, including more elision. In no particular order:
https://github.com/rust-lang/rfcs/pull/2115
However, the compiler could (and did, I believe) run inference and suggest a fix that the programmer can explicitly include.
Granted Rust has some paradigms and constructs which are not easy to learn, I found it rather exciting. I think it has future scope.
Wonder whats happening with Redox. I hope Rust adds more libraries, especially network related, since the networked world is increasingly looking like a distributed OS of sort. Browsers are looking like an OS or a shell inside the OS. Browsers are getting more complex with more functionalities added every few months. Not sure I expressed my thoughts correctly, but I guess one can understand what I mean.
Rust should move away from C standard library, if possible.
They've been involved in Google Summer of Code, and so have had lots of status update posts lately, here's the latest: https://redox-os.org/news/gsoc-self-hosting-final/
> Rust should move away from C standard library, if possible.
It's not always possible, but on systems where it is, there's some ability to do so, see https://github.com/japaric/steed
>It's not always possible, but on systems where it is, there's some ability to do so, see https://github.com/japaric/steed
Doesn't linking to it make a Rust program "unsafe", in the Rust sense? Or my understanding is probably not correct.