-
Notifications
You must be signed in to change notification settings - Fork 547
./x.py check #84
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
Comments
@nikomatsakis @mark-i-m - can I take this easy issue? |
Go for it :) |
@nikomatsakis - I've updated the this file correct? |
@nikomatsakis @mark-i-m - I see documentation related to https://forge.rust-lang.org/x-py.html. |
Yep, that's the right file. It already had content on some of the other x.py commands, but not for
Hmm... I think it would be good to do, but not in this PR. I also think it is distinct from #98... Could you open a new issue for it? |
I will update the below content in that file. Please let me know if it is fine.
Also, I will open new issue move copying contents from https://forge.rust-lang.org/x-py.html. |
Ping @rajcspsg Any updates? |
@mark-i-m I've created new issue #130 for documentation from https://forge.rust-lang.org/x-py.html. |
@rajcspsg Thanks! |
So I've recently discovered that
./x.py check
is actually really dang fast -- we should add a note about it in the "how to build compiler" section. It's in particular very useful when you're doing some kind of "type-based refactoring", like renaming a method, or changing the signature of some function.The text was updated successfully, but these errors were encountered: