High level folks complain it takes too long to code in and is hard to understand the borrow checker.
Low level folks complain it takes too long to code in and is hard to understand the borrow checker.
Honestly though the borrow checker is a great compromise to idiot proof memory leak prevention, and the C folks can just throw in unsafe when they want start slinging pointers and manual heap management.
The macro system alone is so good I don’t think it’s fair to appraise the language until you’ve written a dozen macros
@MakeAvoy@snaggen Have you ever written a recursive macro with multiple variadic arguments, my friend? It is so cursed, yet so good when it works (if it works).
Declarative macros are hard to read, same level as regex
Procedural macros require to write a new crate with a ton of boilerplate, sometimes for stuff conceptually really simple (like hash is: apply the same function to every field, then compose the results)
I agree, though, that it’s better there’re here than nothing. It’s just that there is to be a better solution.
High level folks complain it takes too long to code in and is hard to understand the borrow checker. Low level folks complain it takes too long to code in and is hard to understand the borrow checker. Honestly though the borrow checker is a great compromise to idiot proof memory leak prevention, and the C folks can just throw in unsafe when they want start slinging pointers and manual heap management. The macro system alone is so good I don’t think it’s fair to appraise the language until you’ve written a dozen macros
@MakeAvoy @snaggen Have you ever written a recursive macro with multiple variadic arguments, my friend? It is so cursed, yet so good when it works (if it works).
I’d argue the macros are quite bad:
I agree, though, that it’s better there’re here than nothing. It’s just that there is to be a better solution.