Viewing profile — eriksvedang

OK, I see what you mean now. Thanks for the feedback, I'll make sure to think about this more before stabilising the modules.

The ”IO_” part is the namespace, so no clashes!

Normal usage of arrays (and structs) is through an immutable api, internally it uses mutation though. See example/updating.carp for example.

Correct, not at the moment. Overall the type system is less expressive but also less dependent on annotations. Differentiating between immutable and mutable refs is probably coming…

Primarily stand-alone.

Thanks for the links! The short answer is that safety is handled similar to Rust, using lifetime analysis. It's quite a bit more simplistic than Rust at the moment though. Also, so…

It will require roughly the same amount of practice as when learning Rust, so a pretty significant learning effort I'm afraid. I'll try to do as much checking as possible in the in…

No tail recursion at the moment but it's something I'd be interested in adding later. I'm being very conservative with adding different type constructs but sure, Rust & Go certainl…

Interesting, thanks a lot for the tip!

Yes, only the statically compiled code is GC free.

1. Yes, and yes! 2. No plans for inheritance at the moment, probably some kind of interfaces but that's not a top priority right now. Custom types are limited to structs, I will ad…

Absolutely! We have a gitter chat that would be a perfect place for that kind of discussion https://gitter.im/eriksvedang/Carp

I'm working on Clojure-looking lisp with a borrow checker and static analysis in the vein of Rust. It's especially tailored for games since most lisps don't account for that use ca…