Post B49ycKzt5GiXP1catU by a1ba@suya.place
(DIR) More posts by a1ba@suya.place
(DIR) Post #B49ycJ6u6D8pYCtAYK by thomy2000@fosstodon.org
0 likes, 0 repeats
I don't think most #Rust developers appreciate just how well rust-analyzer works. It handles the most complex types without problems. It suggests basic code improvements. Sure, it takes a while to start, but how often does one restart their editor really...Meanwhile in C/C++ land...https://github.com/clangd/clangd/issues/376
(DIR) Post #B49ycJdW8xEHBM9DO4 by mittorn@masturbated.one
0 likes, 0 repeats
@thomy2000 but will rust work without llvm?
(DIR) Post #B49ycJy4uVfyD7ldR2 by thomy2000@fosstodon.org
0 likes, 0 repeats
@mittorn No, and LLVM is a really cool project. I'm not saying that C/C++/LLVM/... are bad. I just think the development experience with those are not as good as with Rust which has absolutely incredible, reliable tooling.
(DIR) Post #B49ycKPjFhnHashiXA by mittorn@masturbated.one
0 likes, 0 repeats
@thomy2000 i don't like llvm because it's development process is not much open. Everyone may fork it with closed source, and it's maintained by big corps, but it's almost impossible to maintain llvm fork if you not a big corp. Many new languages assumes llvm availiable everywhere, so I see a single failure point in hard llvm dependency. That's reason i preventing getting rust and llvm in my system dependency tree (even if rust-based solutions works better than c++ alternatives)Yes, i using llvm and rust-depended projects for development purposes, but not as part of system. Things like rusticl, rsvg, firefox, nvk, python-cryptography are banned from my system at least until gccrs will be able to build it. Because i cannot fork llvm and maintain it if something goes wrong with it. And sometimes it goes. For example, you cannot compile clang's Registry.cpp with only 2GB ram availiable and there is no solution for it. While this unlikely to be a real blocker, i will force base system to work without llvm while possible.For rustc, i think, it should be possible to run it without llvm or use mrustc instead, but getting this to work with existing always-updated crates and cargo ecosystem would be difficult, so i'll better wait if someone solve thisI cannot agree about rust tooling too, for example, remember what Torvalds said about rustfmt:https://www.phoronix.com/news/Linus-Torvalds-Rust-FormattingEvery tooling have it's issues. clang is focused on C++, so it may glitch on C, clang format does not support many popular readable patterns, and rustfmt collapses some code to unreadable spaghetti. uncrustify does not work as library, only formatting entire file, and qtcreator's internal formatter breaks on some c++ lambdas. In real world there are no ideal things
(DIR) Post #B49ycKzt5GiXP1catU by a1ba@suya.place
0 likes, 0 repeats
@mittorn @thomy2000 btw there is gcc rust backend now, as gccrs seem to be stalled implementing the frontend...so sometimes things are getting better