could not compile `salsa-2022-tests` (test "tracked-struct-field-bad-eq") due to 1 previous error

The process '/home/runner/.cargo/bin/cargo' failed with exit code 101

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

useless conversion to the same type: `impl std::iter::Iterator<Item = &salsa_struct::SalsaField>`

the borrowed expression implements the required traits

usage of `Iterator::fold` on a type that implements `Try`

`salsa-2022-macros` (lib) generated 3 warnings (run `cargo clippy --fix --lib -p salsa-2022-macros` to apply 2 suggestions)

unused import: `plumbing::transmute_lifetime`

use of deprecated method `indexmap::IndexSet::<T, S>::remove`: `remove` disrupts the set order -- use `swap_remove` or `shift_remove` for explicit behavior.

the following explicit lifetimes could be elided: 'b

manual implementation of `BuildHasher::hash_one`

unsafe function's docs miss `# Safety` section