This isn't a Rust subset, but if I were doing memory-safety for a compiled lang, I'd consider making mutability and ability to hold reference/pointer to objects mutually exclusive. Ref tracking then becomes easy without heavy runtime machinery.
-
-
-
Yeah, that’s what Cyclone did. I’m not sure it would be expressive enough, but worth a try.
- 1 more reply
New conversation -
-
-
I think some people would perceive Rust to be a smaller language if the commitment to zero-cost abstractions was dropped and nothing else was changed (I believe
@withoutboats had some interesting thoughts on this). -
you're not wrong, but this is a case for a _different_ language, not for dropping that commitment in Rust, IMO. there are many use-cases where Rust is close to the only acceptable option other than C...
- 7 more replies
New conversation -
-
-
I would say, about Rust, that it has approximately the perfect number and shape of features for a systems language -- it's telling, at least for me, that even when I try to design a "better, cleaner Rust", it ends up being a transform without much cutting or additions
-
The only things I'd consider "redesigning" (or just tweaking) are things there's no _real_ lang-design consensus on "how to do right" anyway: implicits, errors, async, effects-purity-constness, and the visible toggles(s) between static-monomorphic & runtime-polymorphic.
- 1 more reply
New conversation -
-
-
Just add a garbage collector, problem solved! Unless you care about any of the things I care about (like embedded)https://twitter.com/MattHartstonge/status/1150608280135147522 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I think the smaller language is less concerned with absolute performance, but still concerned with being much faster than Go. This language doesn't need "references", just permissions (which eliminates & and * juggling).
@nikomatsakis@jntrnr and I prototyped this in Lark. -
Also, while Lark feels simpler/smaller, there are some ways in which it is "bigger", which I think would ultimately be true about any "smaller, easier rust".
End of conversation
New conversation -
-
-
I know exactly which feature I'd take out -- raw pointers :P
-
(specifically, I'd turn the language abstraction into a library abstraction)
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
