Sebastian Dröge
Sebastian Dröge
With 1.83 we're using cargo nextest 0.9.94, which includes the fix for https://github.com/nextest-rs/nextest/issues/1298 at least.
This generally looks great and useful, but there's one aspect that seems a bit strange to me. From my understanding, to link to such a shared crate you would need...
Sounds good to me, thanks for the fast response :) Maybe you could extend the "A tool to create a stripped, 'dynamic import only' version [...]" item in the "future...
Still not ready :upside_down_face:
It would seem more useful to use Rust APIs for this kind of tasks. If you want to provide a PR that adds bindings for the functions, I'd review that,...
Unless you reimplement all of cargo or just call cargo, Rust support in meson is going to be useless. Everything is using lots of other crates and nobody is going...
> toml seems to be ~1k LoC, maybe only a subset would be needed but annoying no matter. Also toml is just the file format, a more well-defined INI style...
The problem is that you don't even know if foo can be reused at all: it might have different, incompatible configurations for example. Cargo knows how to handle that though....
> @sdroege Calling Meson's Rust support useless for not directly calling Cargo is like calling it's C support useless for not calling Autotools directly. Not really. Autotools is not really...
https://github.com/rust-lang/rfcs/pull/2136 This is very relevant here and meson people probably want to get involved into those discussions. Especially the example of bazel given there sounds like more or less how...