Stream: t-compiler

Topic: running lexer test suite


matklad (Apr 04 2019 at 09:29, on Zulip):

What would be the best command to test changes to the lexer?

I am currently using ./x.py -i --stage 1 test src/test/ui src/test/run-pass src/test/compile-fail/, is there anything better?

centril (Apr 04 2019 at 09:47, on Zulip):

@matklad fastest way would be to cargo foobar in src/libsyntax I think

centril (Apr 04 2019 at 09:48, on Zulip):

that only works if you can roll your unit tests there tho

pnkfelix (Apr 04 2019 at 09:49, on Zulip):

there are dedicated parser tests in src/test/ui/parser, so if you want to narrow your focus, I'd just feed in that path.

pnkfelix (Apr 04 2019 at 09:51, on Zulip):

(also, "better" is slightly ambiguous in your original question: Are you trying to minimize testing time? Or maximize coverage? Or minimize rustc recompile times?)

matklad (Apr 04 2019 at 09:53, on Zulip):

What I am trying to do is to extract the actual lexing part of the lexer (as opposed to interning, span management and all that stuff) into a separate crate. So, I am doing a refactoring, and interested in maximally fast rebuilds with 90% condidence that I didn't break stuff

Last update: Nov 16 2019 at 01:45UTC