Memory Safety Without Borrow Checking, Reference Counting, or Garbage Collection

Re:Memory Safety Without Borrow Checking, Reference Counting... by rurban on Friday June 16, 2023 @02:56AM (#36352513)

Now he just needs to look into parrot (the old perl6 vm) or pony, which do expand on single ownership and compiler-checked move semantics.

Not just memory safe, but also concurrency safe.

Concurrent Pascal was also similar.

[ Parent | on HN ]

Re:Memory Safety Without Borrow Checking, Reference Counting... by Hardliner66 on Friday June 16, 2023 @03:15AM (#36352683)

I think Pony is one of the most interesting languages out there. I love actors, I love capabilities, I love whitelisting of C/C++ usage. Sadly no armv7 support, cross compiling itself is really hard too (never got it to work), the package management support is weird and deviates quite a bit from mainstream (IIRC having multiple versions of the same dependency is a feature ) and it lacks users.

I honestly would love to have a mix between rust and pony.

[ Parent | on HN ]

Re:Memory Safety Without Borrow Checking, Reference Counting... by perlgeek on Friday June 16, 2023 @01:02PM (#36360031)

Too bad nobody was ever able to build a practical, concurrent programming language on top of parrot. (Nor any well-performing non-concurrent language, for that matter). And quite a few talented compiler writers tried (I'm thinking of Patrick Michaud and Jonathan Worthington at least, probably forget quite a few).

[ Parent | on HN ]