Add an option to emit compiler warnings when using 'rustc --parse-only' #3808

Activity

1. brson commented on Oct 22, 2012

   

   brson

   on Oct 22, 2012

   Contributor

   More actions

   --parse-only results in no analysis being performed, so only syntax errors can be emitted. When I run rustc --parse-only over a file with invalid syntax I see the error. The parser doesn't appear to contain any warnings and only one 'note' (for duplicate drop blocks in structs), but I do see that emitted.
2. catamorphism commented on Oct 25, 2012

   

   catamorphism

   on Oct 25, 2012

   Contributor

   More actions

   Closing because this isn't really feasible (linting comes after many other passes that get skipped with --parse-only.)
3. catamorphism

   closed this as completedon Oct 25, 2012
4. Ghoughpteighbteau commented on Jan 20, 2014

   

   Ghoughpteighbteau

   on Jan 20, 2014

   More actions

   can we get a recommendation from one of the devs as to what arguments we should use if we are checking the syntax of a file for correctness? For error and warning highlighting.
5. pnkfelix commented on Jan 21, 2014

   

   pnkfelix

   on Jan 21, 2014

   Contributor

   More actions

   @Ghoughpteighbteau I'm guessing that since the lints use much info from the analysis passes, you still need those, so --no-analysis is not good enough.

   Thus I suspect --no-trans is the best you can do.
6. capdevc

   added 3 commits that reference this issue on Jan 22, 2014

   change rustc invocation to --no-trans

   ...

   630721a

   change rustc invocation to --no-trans

   ...

   ea667f6

   Update/fix to rust checker.

   ...

   217fffa
7. Hi-Angel commented on Apr 21, 2019

   

   Hi-Angel

   on Apr 21, 2019

   More actions

   Neither option works for me.

   $ rustc main.rs --no-trans
   error: Unrecognized option: 'no-trans'
   
   $ rustc main.rs --parse-only
   error: Unrecognized option: 'parse-only'
   
8. jonas-schievink commented on Apr 21, 2019

   

   jonas-schievink

   on Apr 21, 2019

   Contributor

   More actions

   @Hi-Angel you probably want to use cargo check, which uses rustc --emit=metadata internally. This thread is extremely old, things have changed a lot since then.
9. bors

   added a commit that references this issue on May 15, 2021

   tests: add more merge_import tests for rust-lang#3808

   634e244
10. RalfJung

    added a commit that references this issue on Sep 17, 2024

    Auto merge of rust-lang#3867 - DeSevilla:rename-fd, r=RalfJung

    ...

    This issue will close once commit e6604ea is merged into the 'main' branch.

    e6604ea
11. U007D

    added a commit that references this issue on Aug 21, 2026

    Merge rust-lang#3808

    ...

    aaf100f