Sergey "Shnatsel" Davidoff
Sergey "Shnatsel" Davidoff
Reopening now that `cargo audit` supports lockfile v4, but this action reportedly doesn't.
@dependabot rebase
@kornelski `toml` may have leaked into the public API through the error types. I'm curious why this is needed - does the upgrade justify a semver break?
Hmm, we should have support for this already with `--features` flag to select the features of your project that will be considered active, and Cargo feature resolution should take it...
`cargo cyclonedx` relies on `cargo metadata` because `cargo tree` does not provide a machine-readable output. We should be passing the right feature combinations to `cargo metadata` for the top-level project....
I still actively maintain https://github.com/rust-secure-code/cargo-auditable so I don't think I should step away from the WG just yet. cargo-audit also depends on crates from the cargo-auditable repository.
I like the idea, I'll take a look at the implementation later. Thanks!
That seems legit to me. I'd appreciate a PR I could directly benchmark and inspect the generated assembly. We might even be able to create a `const FORWARD: [usize; BLOCK_WIDTH]...
Simply processing the data in 128-bit chunks with something like `chunks_exact` or `as_chunks` might already be enough for the compiler to vectorize the code. Wider chunks don't really make a...
I'm afraid that any pixel-oriented API is going to be too slow to be practical. This includes the current pixel-oriented view APIs in `image`. There are two problems with that...