Is there a disdain for Rust from the Mojo team?
I read Chris' proposal on naming of provenance.
I don't understand why can't we just adopt Rust's convention of using
Mojo is unique on its own:
1) It does ASAP destructors.
2) It provides APIs to low level MLIR artefacts.
There is really, in my humble opinion, NO NEED to be 'different' in areas where it won't make a huge difference.
And also, why is there a subtle leaning on implementing features that are more closely associated to C++ (i.e.
I don't understand why can't we just adopt Rust's convention of using
&'a T and &'a mut T instead of going one round of inventing new keywords ref[lifetime] and refmut[lifetime].Mojo is unique on its own:
1) It does ASAP destructors.
2) It provides APIs to low level MLIR artefacts.
There is really, in my humble opinion, NO NEED to be 'different' in areas where it won't make a huge difference.
And also, why is there a subtle leaning on implementing features that are more closely associated to C++ (i.e.
__copyinit__, a.k.a. copy ctor, etc), whereas there is an aversion to associate itself with Rust? Rust has done many things right, in terms of provenance tracking, quality of life enhancements, ergonomics and beautiful syntaxes. Even a 'safe' version of C++ has no-shame 'copying' Rust features, why should Mojo be ascribed to this aversion?GitHub
The Mojo Programming Language. Contribute to modularml/mojo development by creating an account on GitHub.
