Skip to content

librustc: Pass through extra parameters in automatically-derived methods - #3971

Closed
pcwalton wants to merge 1 commit into
rust-lang:incomingfrom
pcwalton:deriving-pass-through
Closed

librustc: Pass through extra parameters in automatically-derived methods#3971
pcwalton wants to merge 1 commit into
rust-lang:incomingfrom
pcwalton:deriving-pass-through

Conversation

@pcwalton

Copy link
Copy Markdown
Contributor

r? @brson

@brson

brson commented Nov 14, 2012

Copy link
Copy Markdown
Contributor

r+

@pcwalton pcwalton closed this Nov 21, 2012
RalfJung added a commit to RalfJung/rust that referenced this pull request Nov 10, 2024
store futexes in per-allocation data rather than globally
mati865 pushed a commit to mati865/rust that referenced this pull request Nov 12, 2024
store futexes in per-allocation data rather than globally
U007D pushed a commit to U007D/rust-mos that referenced this pull request Aug 21, 2026
3971: add diagnostics subcommand to rust-analyzer CLI r=JoshMcguigan a=JoshMcguigan

This PR adds a `diagnostics` subcommand to the rust-analyzer CLI. The intent is to detect all diagnostics on a workspace. It returns a non-zero status code if any error diagnostics are detected. Ideally I'd like to run this in CI against the rust analyzer project as a guard against false positives.

```
$ cargo run --release --bin rust-analyzer -- diagnostics .
```

Questions for reviewers:

1. Is this the proper way to get all diagnostics for a workspace? It seems there are at least a few ways this can be done, and I'm not sure if this is the most appropriate mechanism to do this.
2. It currently prints out the relative file path as it is collecting diagnostics, but it doesn't print the crate name. Since the file name is relative to the crate there can be repeated names, so it would be nice to print some identifier for the crate as well, but it wasn't clear to me how best to accomplish this. 

Co-authored-by: Josh Mcguigan <joshmcg88@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants