-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
compiletest should check for possible typos in annotated test directives #83551
Comments
@rustbot label: A-testsuite |
Is this to distinguish an ordinary comment from a directive? |
@osa1 |
This is easier if/when we port over all current Other bootstrap tools like tidy should also probably use something else to distinguish them from regular comments. Otherwise, trying to check between a valid directive vs comment is really cursed, and comments like
gets treated as |
…o-check, r=onur-ozkan Detect typos for compiletest test directives Checks directives against a known list of compiletest directives collected during migration from legacy-style compiletest directives. A suggestion for the best matching known directive will be made if an invalid directive is found. This PR does not attempt to implement checks for Makefile directives because they still have the problem of regular comments and directives sharing the same comment prefix `#`. Closes rust-lang#83551.
…o-check, r=onur-ozkan Detect typos for compiletest test directives Checks directives against a known list of compiletest directives collected during migration from legacy-style compiletest directives. A suggestion for the best matching known directive will be made if an invalid directive is found. This PR does not attempt to implement checks for Makefile directives because they still have the problem of regular comments and directives sharing the same comment prefix `#`. Closes rust-lang#83551.
This should help with things like #83348 (comment)
Levenshtein distance with list of known directives will be enough?
The text was updated successfully, but these errors were encountered: