Arbitrary mention: Crust[0] [0] https://github.com/tsoding/crust
Wow, it really do look like C
you_can::turn_off_the_borrow_checker
21–24 of 24 posts
Re: you_can::turn_off_the_borrow_checker
#22Earlier quoted context omitted.
Rust macros are Token Trees and provide namespace hygiene, so not quite "text in, text out".
Token list, not token trees. There are official libraries for parsing token stream as rust code but you can parse it as anything (eg json, html) if you want to.
I think you meant TokenStream. They are trees, behind the scenes, because matching delimiters happens early on between lexing and parsing. By the time the rustc_proc_macro::TokenStream is exposed, the rustc_ast::tokenstream::TokenTree is hidden to the proc macro API.
https://doc.rust-lang.org/stable/nightly-rustc/rustc_ast/tok...
https://doc.rust-lang.org/stable/nightly-rustc/rustc_proc_ma...
Re: you_can::turn_off_the_borrow_checker
#23Rust's memory safety is as much a social convention as it is a language feature. The language has something better described as "mutation safety," and it's the job of library developers to use that to design UB-free APIs.
I think many people understand this subconsciously, and that this is what drives some of the more performative security culture in Rust spaces (superfluous safety comments, shunning of certain crate authors, `forbid(unsafe)`, push-back against syntax sugar, etc.).
Re: you_can::turn_off_the_borrow_checker
#24This reminds me of Perl's ACME modules and I'm here for that.
I would go for a Rust version of Acme::Bleach.