| Age | Commit message (Collapse) | Author | Lines |
|
run first
|
|
deps: bump toml from 0.4 to 0.5
changelog: none
|
|
|
|
Fix breakage due to rust-lang/rust#60225
Wrote this up before I saw that Manish already started on a fix in #4038. It no doubt contains errors. Feel free to close.
|
|
|
|
Do not trigger redundant_closure for non-function types
fixes #3898
Added a check for the entity being called in the closure body to be a FnDef. This way lint does not trigger for ADTs (Box) but I'm not sure if it's correct and not too restrictive.
<!--
Thank you for making Clippy better!
We're collecting our changelog from pull request descriptions.
If your PR only updates to the latest nightly, you can leave the
`changelog` entry as `none`. Otherwise, please write a short comment
explaining your change.
If your PR fixes an issue, you can add "fixes #issue_number" into this
PR description. This way the issue will be automatically closed when
your PR is merged.
If you added a new lint, here's a checklist for things that will be
checked during review or continuous integration.
- [ ] Followed [lint naming conventions][lint_naming]
- [ ] Added passing UI tests (including committed `.stderr` file)
- [ ] `cargo test` passes locally
- [ ] Executed `util/dev update_lints`
- [ ] Added lint documentation
- [ ] Run `cargo fmt`
Note that you can skip the above if you are just opening a WIP PR in
order to get feedback.
Delete this line and everything above before opening your PR -->
changelog: Fix false positive in `redundant_closure` pertaining to non-function types
|
|
Attempt to fix #3981
Fixes #3981
Hi, hopefully this is correct, happy to have feedback.
changelog: Don't trigger `unnecessary_cast` inside a macro
|
|
|
|
Update pulldown_cmark to 0.5
We now no longer have to use our own wrapper around `Parser` and can use
the new `OffsetIter`.
changelog: none
|
|
Only run AppVeyor on r+, try and the master branch
As it is right now, there is only one worker available in the `rust-lang-libs`
AppVeyor project and there are other repos as well that we share this worker
with. This has been a problem for us because we sometimes hit a bors timeout if there
are too many builds queued up.
To improve the situation, I think we could try to use AppVeyor a bit less
often. The average PR is not going to break windows related things anyway, so
it should be fine to run it on r+/try/master only.
changelog: none
|
|
Rustup for https://github.com/rust-lang/rust/pull/59042
changelog: none
|
|
|
|
We now no longer have to use our own wrapper around `Parser` and can use
the new `OffsetIter`.
|
|
Remove approx_constant known problems
Fixes #4025.
changelog: Remove `approx_constant`'s documentation's "Known problems" section.
|
|
As it is right now, there is only one worker available in the `rust-lang-libs`
AppVeyor project and there are other repos as well that we share this worker
with. This has been a problem for us because we sometimes hit a bors timeout if there
are too many builds queued up.
To improve the situation, I think we could try to use AppVeyor a bit less
often. The average PR is not going to break windows related things anyway, so
it should be fine to run it on r+/try/master only.
|
|
Add test for or_fun_call macro suggestion
changelog: none
Closes #1018
|
|
Fixes #4025.
|
|
UI test cleanup: Extract needless_range_loop tests
changelog: none
|
|
r=flip1995
Suppress let_and_return if let has attributes
Fixes #3882.
changelog: suppress `let_and_return` if `let` has attributes
|
|
Fixes #3882.
|
|
Closes #1018
|
|
|
|
Change "if types change" to "if you later change the type"
Fixes #3964.
changelog: change wording of `cast_lossless` message
|
|
Fixes #3964.
|
|
Ignore non-const ctor expressions in or_fn_call
Fixes https://github.com/rust-lang/rust-clippy/issues/1338
Should have been fixed by #919, however that focuses on const ctor expressions only, and `.or(Some(local))` isn't const.
This also automatically ignores things like `.or(Some(local.clone())` which we don't actually want to do; I need to figure out what to do here.
changelog: Fixed false positive in [`or_fn_call`] pertaining to enum variant constructors
r? @oli-obk @phansch
|
|
Rustup to rustc 1.36.0-nightly (fe0a415b4 2019-04-23)
r? @oli-obk @phansch
|
|
|
|
|
|
|
|
compiletest: Disambiguate extern crate deps shared with the compiler
Fixes #4015.
changelog: Handle deps shared with the compiler in the internal compiletest suite
Attempts to fix the multiple matching crates error using the `--extern dep=path` disambiguation. This only includes `serde` at the moment because it's the only problematic dep right now (is inside Rust sysroot and pulled via `extern crate` in the test suite).
I'm not exactly sure this is the right approach (FWIW it fixes the issue locally), please do tell if this should be done differently.
|
|
|
|
r=matthiaskrgr
Move path_buf_push_overwrite to nursery
See #4012.
changelog: move `path_buf_push_overwrite` to the nursery
|
|
rustup: Use newly-introduced mutability query for statics
Fixes fallout from https://github.com/rust-lang/rust/pull/60124.
cc https://github.com/rust-lang/rust/issues/60154
changelog: none
|
|
Fixes fallout from https://github.com/rust-lang/rust/pull/60124.
cc https://github.com/rust-lang/rust/issues/60154
|
|
See #4012.
|
|
|
|
Add test for derives for used_underscore_binding lint
This closes #852 as I can't reproduce the original issue anymore.
changelog: none
|
|
Allow allowing of toplevel_ref_arg lint
I'm not sure why some lints need the `HirId` to be able to recognize the
lint level attributes, but this commit makes the lint level attributes
work for `toplevel_ref_arg`.
Fixes #2332
changelog: Allow allowing of `toplevel_ref_arg` lint
|
|
Add run-rustfix for match_as_ref lint
* Extracts `match_as_ref` into separate file
* Adds `// run-rustfix` to `tests/ui/match_as_ref.rs`
cc #3630
changelog: none
|
|
Fix false positive in module_name_repetitions lint
This lint was triggering on modules inside expanded attrs, like
for example `#[cfg(test)]` and possibly more.
It was not reporting a location in #3892 because `span.lo()` and `span.hi()` both were 0.
Fixes #3892
changelog: Fix false positive in `module_name_repetitions` lint
|
|
This closes #852 as I can't reproduce the original issue anymore.
|
|
Update compiletest_rs
This includes a fix that make ICEs appear in UI tests again.
|
|
This includes a fix that make ICEs appear in UI tests again.
|
|
I'm not sure why some lints need the `HirId` to be able to recognize the
lint level attributes, but this commit makes the lint level attributes
work for `toplevel_ref_arg`.
|
|
|
|
This lint was triggering on modules inside expanded attrs, like
for example `#[cfg(test)]` and possibly more.
|
|
* Extracts `match_as_ref` into separate file
* Adds `// run-rustfix` to `tests/ui/match_as_ref.rs`
|
|
Don't trigger assertions_on_constants on debug_assert!(false)
Fixes #3948
Fixes #3765
changelog: Fix `debug_assert!` false positive on `assertions_on_constants` lint
|
|
Typo
changelog: none
|
|
Add run-rustfix for len_zero lint
* Extracts len_without_is_empty into separate file
* Adds `// run-rustfix` to `tests/ui/len_zero.rs`
cc #3630
|