-
Notifications
You must be signed in to change notification settings - Fork 707
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
Remove Type::detect_has_vtable_cycle. #787
Remove Type::detect_has_vtable_cycle. #787
Conversation
r? @fitzgen |
Can you squash the commits please? Thanks! |
After some discussion in rust-lang#765 we do not think anymore this it can ever be true.
1850ba8
to
672b740
Compare
@emilio Done. My 2c: In my humble opinion this should be done by the merge bot. It is quite useful to keep the history of the commits in the related PR to see the development of the discussion and GitHub does not deal well with rebasing. GitHubs own merge tools actually allow for that - squashing everything into one commit on merge. The mergebot could do that too - the only question is which commit message to use. In my projects the tradition is to use the OP as the commit message and edit it to always reflect the state of the PR. |
@bors-servo r=emilio |
📌 Commit 672b740 has been approved by |
Remove Type::detect_has_vtable_cycle. After some discussion in #765 we do not think anymore that this can ever be true.
☀️ Test successful - status-travis |
After some discussion in #765 we do not think anymore that this can ever be true.