Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I mean, why not just write Rust at that point? Required static typing is fundamentally at odds with the design intent of the language.


A lot of people want a garbage collected Rust without all the complexity caused by borrow checking rules. I guess it's because Rust is genuinely a great language even if you ignore that part of it.


Isn't garbage collected Rust without a borrow checker just OCaml?


Pretty much, I would say, in fact, I like OCaml better if we put the borrow checker aside.


Thankfully, like many other languages that rather combine models instead of going full speed into affine types, OCaml is getting both.

Besides the effects type system initially introduced to support multicore OCaml, Jane Street is sponsoring the work for explicit stack allocation, unboxed types, modal types.

See their YouTube channel.


Yeah, I have watched a couple of videos and read blog posts from Jane Street. They are helping OCaml a lot!


Or even better imo, Reason ML.


I have not used Reason ML as I have not had the reason to. :D

But apparently the target audience is JavaScript / TypeScript developers, and I think it is mainly used for web development IIRC, whereas OCaml is much more general-purpose and even low-level at times.

Jane Street is doing a great job at contributing to OCaml itself and its libraries.


I didn't use it for JS at all, I used it for the sane syntax.


> a garbage collected Rust

By the way, wouldn't it be possible to have a garbage-collecting container in Rust? Where all the various objects are owned by the container, and available for as long as they are reachable from a borrowed object.


Isn't this what Rc is?


Only for synchronous immutable data.


D and Go exist.

There are alternatives out there


Is Go that language?


Rust syntax is much nicer than go. Also enums


Not only that: Rust is considerably faster and more reliable. Since you're not writing the code yourself, Rust would be an objectively better choice.

Who are we trying to fool?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: