What are protental issues with compiler, by just disabling borrow checker? If I recall correctly some compiler optimisations for rust can not be done in C/C++ because of restrictions implied by borrow checker.
Rust--: Rust without the borrow checker
21–30 of 269 posts
Re: Rust--: Rust without the borrow checker
#22Re: Rust--: Rust without the borrow checker
#23I am wondering whether this would actually be a helpful compile option in upstream rustc for quick prototyping. I don't want prod code to use this, but if I want to try things out during development, this could substantially shorten the dev cycle.
Re: Rust--: Rust without the borrow checker
#24Re: Rust--: Rust without the borrow checker
#25Re: Rust--: Rust without the borrow checker
#26Tangentially related: the opposite, Rust's borrow checker sans the compiler, is actually very useful. As far as I understand, the borrow checker is a significant part of the work of writing a Rust compiler. Therefore, having the official borrow checker available as a standalone program can make alternative compilers (e.g. for exotic hardware) feasible faster, because they won't need a borrow checker of their own from…
Re: Rust--: Rust without the borrow checker
#27Re: Rust--: Rust without the borrow checker
#28I wish I could make the borrow checker give warnings not errors. It would make exploration so much easier, so I don’t have to fight the borrow checker until I know how to build what I want.
I think fighting the borrow checker is more like a rite of passage. Rust is not my favorite language but the borrow checker is great.
Re: Rust--: Rust without the borrow checker
#29I wish they made something simpler. At least C and C++ have a low barrier of entry and any beginner can write code.
I don't think the borrow checker forced rust to be such a complicated language.