Age | Commit message (Collapse) | Author |
|
* 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.
|
|
Fix #1684: Use the correct flag name in rustc linter
|
|
The rust compiler renamed the option '-Z no-trans' to '-Z no-codegen'.
https://github.com/rust-lang/rust-enhanced/issues/281
|
|
|
|
|
|
* 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
|
|
|
|
|
|
This removes the argument if the specified toolchain is empty.
As far as I can tell there is no +nighly (or similar) option [1] leading to
the termination of the server. But since people needed this option and
have yet to complain about it it stays the default for now.
[1] https://github.com/rust-lang-nursery/rls/blob/master/src/main.rs#L87
|
|
* 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
|
|
|
|
|
|
rename the Rust LSP linter to `rls`
|
|
|
|
|
|
|
|
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.
|
|
and disable the rust linters for now, re #256"
This reverts commit f412b4f96fa49f4ed856db25c10bdf4b9c2e4cec.
Conflicts:
doc/ale.txt
|
|
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
|