resurrectedcyb

8 ms·

1. 1.▲
   by resurrectedcyb 1y ago

   That project had 'cargo check' take 15-20 minutes, though it might not have been indicative, the submitter posted an update about how it was fixed. This may be a better example. https://github.com/rust-lang/ru
2. 2.▲
   by resurrectedcyb 1y ago

   Interesting. The change to sets of loans is interesting. Datalog, related to Prolog, is not a language family I have a lot of experience with, only a smidgen. They use some kind of solving as I recall, and are great at certain types of prob
3. 3.▲
   by resurrectedcyb 1y ago

   I have actually seen a few posts here and there of 'cargo check' being slow. I have also heard of complaints of rust-analyzer being slow, though rust-analyzer may be doing more than just 'cargo check'. https:/&#x2F
4. 4.▲
   by resurrectedcyb 1y ago

   Is there any tool for Rust that does profiling that detects what part of compilation time is caused by what? Like, a tool that reports: - Parsing: x ms - Type checking: y ms - LLVM IR generation: z ms And have there been any statistics done
5. 5.▲
   by resurrectedcyb 1y ago

   I do not know if the borrow checker and Rust's type system have been formalized. There are stacked borrows and tree borrows, and other languages experimenting with features similar to borrow checking, but without formal algorithms like
6. 6.▲
   by resurrectedcyb 1y ago

   I don't see that debunking it. Instead, it says "usually". That means that it depends on the project. There is definitely Rust code that takes exponential time to compile, borrow checker or not. https://play.rust-l