Faith Ekstrand
A bit annoyed by the documentation situation with #rustLang... As with most things in Rust land, it's great if you use cargo and it really sucks if you don't.
Unlike rustfmt, rustdoc actually has to be able to compile the code so it needs access to all your dependencies. You can't just invoke rustdoc on foo.rs and call it a day. It really needs to be invoked by the build system. Worse, it doesn't support all the same flags as rustc, some of which are used by meson.
Kristian H. Kristensen
@gfxstrand I'll admit to having thought, "if I just rewrite enough of the project in rust, we could switch to cargo and just use meson for the remaining C/C++ parts."
Neal Gompa (ニール・ゴンパ) :fedora:
@krh @gfxstrand It's easy enough to see Rust is actively hostile to external build systems, though. It's really difficult to use Rust in a non-Cargo context and they don't have nice things to say when you ask for help trying to do it.
That being said, I was soured on Meson for different reasons (mostly the unstable behavior/API from version to version) and generally prefer to use CMake.
Kristian H. Kristensen
@gfxstrand Meson is actively hostile towards rust and it has really soured me on meson. Declarative build system sounds nice until you realize what a gatekeeper it is.
Faith Ekstrand
I mean, it makes sense why they do that. You want to be able to run proc macros so you can determine auto-derived traits and stuff like that. Also, rustdoc for one package will generate links to docs for other packages which is pretty neat. You can't really do that without compiling and tying into cargo. Unfortunately, as with a lot of other stuff, that leaves those of us trying to use other build systems in a real pickle.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.