Getting Past “Ampersand-Driven Development” in Rust

• hylo

  54 1,104 9.9 Swift

  The Hylo programming language

  

See Val for a possible step into that direction.

https://www.val-lang.dev/

Or how the Chapel language for HPC is going at it,

https://chapel-lang.org/

• chapel

  26 1,739 10.0 Chapel

  a Productive Parallel Programming Language

  

See Val for a possible step into that direction.

https://www.val-lang.dev/

Or how the Chapel language for HPC is going at it,

https://chapel-lang.org/

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• Vale

  64 1,672 6.8 Scala

  Compiler for the Vale programming language - http://vale.dev/ (by ValeLang)

  

> I've been wondering lately whether a new spatial approach can yet again simplify matters.

I've been closely following the development of Vale since I first saw it here. Though their approach is slightly higher-level than Rust and requires (some) runtime safety checks (though to be fair, so does GC).

https://vale.dev/

https://verdagon.dev/blog/zero-cost-memory-safety-regions-ov...

I think it would be tough to change the spatial model in a language as low-level as Rust, because that spatial model is just reflecting how your CPU actually works under the hood. If you try to hide that away, the programmer is going to end up losing some control.

• csp-cso-chipmunk-

  1 2 10.0

  chipmunk- \x ()

Very cool. I will take a look. This * was a (just) sketch I did years ago starting from a CSP base (Go). Explicit spaces (or "regions") and defined transition semantics (which compiler and runtime can enforce and guarantee). Single ownership spaces also make distributed GC so much simpler.

*https://github.com/alphazero/csp-cso-chipmunk-

Suggest a related project