Mateusz Kowalczyk
Mateusz Kowalczyk
`crate2nix` generates things like these in `Cargo.nix`: ```nix "tsu-mini-std" = rec { crateName = "tsu-mini-std"; version = "0.1.0"; edition = "2021"; # We can't filter paths with references in Nix...
Currently whenever Cargo.lock changes, developer has to notice and run `crate2nix` manually. This is annoying but I can't think of simple way to automate this away that's consistent for developers...
We already `tee` the test output. I'm not sure what benefit the `-x` provides except bunch of noise before the output we probably actually care about. Perhaps it's a debugging...
It seems that if a crate contains doctests, `runTests` doesn't run these while `cargo test` does. I don't know what's involved in making this work.
Cargo has a questionable behaviour where ``` cargo build -pfoo cargo build -pbar ``` does not give the same result as ``` cargo build -pfoo -pbar ``` In the first...
Without this, if we do `nix run .#some-workspace-member`, it tries to run `$out/bin/rust_some-workspace-member` as it defaults to the package name. It'd be cool if `nix run .#flake` just worked.
The tag parsers are very easy to crash. Simplest way to replicate is to just feed JSON from one domain to tag parser for another and it's almost certain to...
`parse_xy_img_dimensions` segfaults unless the input is in exactly the expected format; this is both due to not checking that `strstr` is not returning null as well as not checking return...
If `get_distance` is called on non null-terminated `string` that doesn't contain `find` token, it accesses memory on the heap behind the string. I'm attaching a sample file. It may be...
It'd be great if the package could use cabal-supported tests: the existing way is quite inconvenient to run and cabal is not informed about the test dependencies that we need...