-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
internal: don't shut up the compiler when it says the code's buggy #10080
Conversation
Wrapping state-modifying functions into a `catch_unwind` is wrong -- to do retry after failure, you need to have transactional semantics!
Canceled. |
bors r+ |
/// (`on` method). | ||
/// | ||
/// Some read-only requests are latency sensitive, and are immediately handled | ||
/// on the main loop thread (`on_sync`). These are typically typing-related |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Veykril [`RequestDispatcher::on_sync`]
doesn't work for me. Is it our bug, or is this just isn't supported by rustdoc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should work I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ye I'm pretty sure that should work with rustdoc. Odd that we don't resolve this 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh right this is #9694
bors r+
🤖