The Truth

Lisp (scheme, common lisp) and C is all you need.

Try to prove me wrong.

(I haven't posted in this thread since >>23)

>>24
it's not put together randomly, that's why it changes so much. the idea is to stabilize it before 1.0

You're right in that it's unsuited for use today, but by the end of the year that should change. The language is nearly complete, libraries are being finalized. I think [m]std[/m] has been recently.

>>26
uniqueness (affine types) is the main benefit of the language, and it's used to forbid mutable aliasing, with no runtime overhead.

the GC is nothing like D. it was originally planned to work like that because they thought most people would make use of GC, but then the region system turned out way better than anyone thought and GC is entirely optional.

>>30

this is how I call non-pure languages/languages that promote side effects/multi-paradigm languages, so yes

Few others subscribe to a definition of it that doesn't even admit Haskell. If for no other reason, such a term would be valueless in common currency.

How about an actual problem for Rust in this area: higher-order programming is weak because closures are utilitarian at the moment. It's a shame, but there's a concrete plan to fix it.

>>36
By linking them and calling into them. At your option.