https://bugs.kde.org/show_bug.cgi?id=448087

--- Comment #3 from Andreas Grois <[email protected]> ---
Sorry, this is not really relevant to the bug, but I just have to correct
myself here. I was too tired yesterday to realize that also the &mut self ->
&self situation can cause issues. Actually #406178 describes such a call stack.
With Rust's aliasing rules the compiler can assume that the call to C++ (which
does not take any references into the memory pointed to by &mut self) is
independent of &mut self, so it need not guarantee that the memory referenced
by &mut self is in a consistent (or up-to-date) state when it triggers the
signal.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to