Skip to content

Use --parse-only by default with rustc. #1114

Closed
wants to merge 1 commit into from

2 participants

@BurntSushi

This reverts a previous change to use --no-trans by default when
calling the Rust compiler. --no-trans is a more useful mode, but
doesn't quite fit with Syntastic's model. Instead, --parse-only
will check that the syntax of a Rust file is valid and it will
always work. --parse-only is a more useful default mode.

@BurntSushi BurntSushi Use --parse-only by default with rustc.
This reverts a previous change to use --no-trans by default when
calling the Rust compiler. --no-trans is a more useful mode, but
doesn't quite fit with Syntastic's model. Instead, --parse-only
will check that the syntax of a Rust file is valid and it will
always work. --parse-only is a more useful *default* mode.
ab42b16
@BurntSushi

This is consistent with using ghc-mod (see #63) for Haskell's syntax checker instead of using ghc proper.

@lcd047 lcd047 added a commit that referenced this pull request Jun 12, 2014
@lcd047 lcd047 Remove the rustc checket for Rust.
Between #947, #1114, and #1112, this checker is too controversial to
maintain in syntastic.  Please consider using it as an external checker
if you need it:

https://github.com/scrooloose/syntastic/wiki/Syntax-Checker-Guide#external
1383c0f
@lcd047
Collaborator
lcd047 commented Jun 12, 2014

Checker removed in 1383c0f. Please see the wiki for maintaining it as an external checker. Please see the discussion at this commit, and the threads #947 and #1112 for more background.

@lcd047 lcd047 closed this Jun 12, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.