Age | Commit message (Collapse) | Author |
|
There is already a `rust_ignore_secondary_spans` option, providing more
hiding of errors than anyone likely can desire.
|
|
(Make cargo work on whole project as documented)
According to `:help ale-integration-rust`, using cargo as a linter should
check the entire project. It appears this was the case initially, but it
broke somewhere along the way.
Setting `filename` to the output in the handler and avoid filtering the
spans on `file_name` goes a long way in restoring the intended behavior.
However test cases fail, even after attempting to update them. Please
see next commit.
|
|
Working directories are now set seperately from the commands so they
can later be swapped out when running linters over projects is
supported, and also better support filename mapping for running linters
on other machines in future.
|
|
This can avoid having to wait for ALE or ALE being blocked on other
cargo actions within the same crate.
|
|
|
|
|
|
|
|
|
|
* Add support for `cargo clippy`
* Add tests for cargo-clippy support
* Add an example to doc for how to configure ale_rust_cargo_use_clippy
|
|
* The project style linter now runs while you type.
* Now the scripts for checking the project require blank lines.
* Many style issues have been found and fixed.
|
|
* Rust Cargo linter: Improve workspace support
When using Cargo workspaces [1], there is a 'Cargo.toml' directory in a
top level directory, listing all the crates in the project. If we are
currently editing one of the crates, 'cargo build' should execute in
that directory for that crate's separate `Cargo.toml`, otherwise Cargo
may spend more time possibly rebuilding the entire workspace, and maybe
failing on one of the other crates, instead of succeeding on the current.
[1] https://doc.rust-lang.org/book/second-edition/ch14-03-cargo-workspaces.html
|
|
|
|
* When working on rust/cargo projects of varying sizes, it may be useful
to either build all possible features (i.e. lint all possible
conditionally compiled code), or even turn off other features for a
quicker edit-lint cycle (e.g. for large projects with large build times)
* Added a g:ale_rust_cargo_default_feature_behavior flag for instructing
cargo to not build any features at all (via `--no-default-features`),
building default features (via no extra flags), or building all possible
features (via `--all-features`)
* Also added a g:ale_rust_cargo_include_features flag for including
arbitrary features to be checked by cargo. When coupled with
g:ale_rust_cargo_default_feature_behavior this allows for full
customization of what features are checked and which ones are ignored
|
|
some of the time.
|
|
|
|
for cargo versions that are new enough
|
|
|
|
|
|
|
|
|
|
on disk
|
|
- Use `cargo check` instead of `cargo build` when
`g:ale_rust_cargo_use_check` is truish.
- Use `--frozen` to avoid locking the project.
|
|
|
|
|
|
and trailing whitespace, and fix existing issues.
|
|
disable the rust linters for now, re #256
|
|
* Add rustc checker for rust files
* Add documentation for rustc
* Use a nice helper function
* Add cargo as linter
* Complete the doc for rust linters
* Put l: in front of every local variable
* Apply the requested stylistic changes
|