Psionic K

You bring up some important considerations. The solutions I'm considering are perhaps looking too far ahead, but I will write them down. > Still, it feels wrong to have to...

Even in a mono-repo, it's trivial to create multiple package sets either from separate flakes or one big flake. I don't really know what the use case was anymore. Moving...

I ran the `check --release` on RustAnalyzer. Significantly more diverse outputs in the artifacts than just `.d` and `.rmeta` Aside, since rust check doesn't need to link or emit binary,...

See reasoning in #92 for not blocking, but also not pursuing more support for non-output Nix derivations

I reproduced the build failure in your example on the release-0.9.1 branch. I believe the features might not be the same with cargo & nix, so you end up missing...

Here's bevy 0.7.0 nix build: https://github.com/psionic-k/bevy-build-example I ran into one hangup with the features I need to check. I had to disable some features on wgpu-hal crate by modifying the...

What I do to fix these is run into `main.rs` and add some `dbg!` to show for which feature activation a `dx12` feature shows up. Once I know that, I...

That's during build phase. When generating the Cargo.nix, we're using cargo 0.61.0 and it can do everything cargo does. Since the extra features show up in Cargo.nix, it's generation that's...

`cargo tree -e features` is helpful to see what the feature expression dependency _should_ look like. Currently in cargo2nix, the goal was to build with all root crates at least...

Looks like another situation where the model is going to need to be more fully implemented. Expressing the intersection of root features and platforms will be expensive. I don't see...