This has a few advantages: we don't have to include the generated file in the
source tree, and using include!() avoids rustfmt and other tools checking the
file.
The location of the generated file can also be customized by setting OUT_DIR,
but cargo picks an appropriate temporary place in the target/ directory by
default.
Also set the default workspace members to the crates which have tests so I don't
have to forget using --workspace all the time.
chore: remove rustfmt.toml
It uses nightly-only options, which have no effect on the output.
The other options are already the default.
refactor: fix clippy suggestions
refactor: get rid of nightly rust dependency
Closes: https://github.com/tjdevries/vim9jit/issues/28
This has a few advantages: we don't have to include the generated file in the source tree, and using
include!()avoids rustfmt and other tools checking the file.The location of the generated file can also be customized by setting
OUT_DIR, but cargo picks an appropriate temporary place in the target/ directory by default.Also set the default workspace members to the crates which have tests so I don't have to forget using
--workspaceall the time.It uses nightly-only options, which have no effect on the output. The other options are already the default.
ci: use rust-cache to speed up CI immensely
docs: misc