Removing Garbage Collection from the Rust Language (2013)

Re:Removing Garbage Collection from the Rust Language (2013) by BenoitP on Monday September 11, 2023 @07:47AM (#37465837)

Java?

* Type system is even accidentally Turing complete

* Very good perf, but language doesn't help by being indirection-friendly. Value types will help a lot.

* SOTA GCs

* Ecosystem big

* Cheap threads now. Don't do async! Just block.

* Structured concurrency soonish

[ Parent | on HN ]

Re:Removing Garbage Collection from the Rust Language (2013) by masklinn on Monday September 11, 2023 @08:02AM (#37465981)

> Type system is even accidentally Turing complete

A turing complete type system is easier to stumble into than to avoid.

That doesn’t mean the type system is expressive. Turing tarpits are turing complete by definition, and nobody would call Thue, Iota, or the average OISC expressive.

[ Parent | on HN ]

Re:Removing Garbage Collection from the Rust Language (2013) by kaba0 on Monday September 11, 2023 @12:20PM (#37469536)

Or if someone really want to play around with types: Scala, especially Scala 3. People can’t even say that it is not nullsafe, as it is.

[ Parent | on HN ]

Re:Removing Garbage Collection from the Rust Language (2013) by Zambyte on Monday September 11, 2023 @01:10PM (#37470289)

I haven't used Scala since 2. Did something change related to null with 3? Can you no longer use null? I know it has the Option type which can be used to safely represent nullable values, but that is (or at least was) in addition to, rather than in replacement of null.

[ Parent | on HN ]

Re:Removing Garbage Collection from the Rust Language (2013) by kaba0 on Monday September 11, 2023 @01:19PM (#37470422)

It has a compiler flag which will remove the null value from most type’s sets, that is a String will never contain null, if you want it to be nullable you have to write `String | None` (or Null? Something like that).

[ Parent | on HN ]