Server list obscures 'kicked' (and other) messages #14140
Comments
|
This repository is for the rust programming language, not the rust game. |
lnicola
pushed a commit
to lnicola/rust
that referenced
this issue
Feb 13, 2023
fix: Fix proc-macro-server incorrectly stripping delimiters 🙄
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Feb 20, 2025
) In the case where `iter` is a `DoubleEndedIterator`, replacing a call to `iter.last()` (which consumes `iter`) by `iter.next_back()` (which requires a mutable reference to `iter`) cannot be done when `iter` is a non-mutable binding which is not a mutable reference. When possible, a local immutable binding is made into a mutable one. Also, the applicability is switched to `MaybeIncorrect` and a note is added to the output when the element types have a significant drop, because the drop order will potentially be modified because `.next_back()` does not consume the iterator nor the elements before the last one. Fix rust-lang#14139 changelog: [`double_ended_iterator_last`]: do not trigger on non-reference immutable receiver, and warn about possible drop order change
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a server restarts or you log out, or get kicked for some reason,
The message that explains what and why is obscured by the 'servers'lobby-window.
Quickly pressing 'options' will let you read part of it.
The text was updated successfully, but these errors were encountered: