I've heard that the compilation time for @rustlang gets progressively long with more code. Is this true ? #Code #Programming
-
-
To this I have two questions: - What kind of macros? (C-style or Lisp style?) - How do you check for memory safety? Rust gives you ownership guarantees at compile time. Maybe that's what makes it much slower to check
-
It's not Rust vs Jai. It's that languages don't have to take ages to compile, even when they provide you with high level features mentioned above. For more details on how Jai is implemented you can check Jon's channel:https://www.youtube.com/user/jblow888
-
I will watch it, but bear in mind that many more things make it slow to compile (among other things, memory safety intersected with aiming to be as fast as good C++). It's not that it's not a priority.
-
Compilation speed is *clearly* not a high priority with Rust. Priorities are balanced against other priorities, and other ones came out way on top.
-
Well that's okay. Correctness and generated code performance are higher priorities.
-
From what I have been told, correctness is not the priority -- "memory safety" is, even in the many cases where memory safety does not lead to correctness.
-
I think that correctness is definitely a priority. Have you seen Ralf Jung's working group research of the `unsafe` uses within the stdlib and the compiler? Unless we're talking about a different form of correctness. I'm mostly talking about avoiding UB and vulnerabilities.
-
Then I think you are using the word "correctness" too loosely and charitably (as I think the entire Rust community does). Avoiding UB and vulnerabilities is good, but correctness means the program doesn't have bugs.
- 19 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.