[rust-qt-binding-generator] [Bug 448087] New: rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 Bug ID: 448087 Summary: rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference. Product: rust-qt-binding-ge

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #2 from Andreas Grois --- I was not aware that there is already work ongoing in that regards. Is this bug report then really a duplicate of 406178? Using internal mutability with a Mutex indeed sounds like the most viable approach. It has

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #3 from Andreas Grois --- 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 #40617

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #4 from Andreas Grois --- I've had a look at the linked branch. That does not only contain the fix for the mutability/aliasing issue, but functionality (replaceable objects) which I don't want/need for my use case. I'v

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #6 from Andreas Grois --- To be honest I haven't spent much thought on the RefCell idea. The plan would have been to replace Box::into_raw(Box::new(d_{})) by Box::into_raw(Box::new(RefCell::new(d_{}))) and all usages of that pointer,

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #7 from Andreas Grois --- I think the first draft of the changes is ready for an initial review, in case you would like to merge them: https://invent.kde.org/sdk/rust-qt-binding-generator/-/merge_requests/2 It's still marked a

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #8 from Andreas Grois --- Correction: The cmake build currently actually works. I didn't try it before, assuming it would just overwrite the Demo's Rust bindings, but obviously that's not the case. -- You are receiving th

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #11 from Andreas Grois --- Thanks! I'll start modifying Demo, ToDo and the tutorial code snippets then. -- You are receiving this mail because: You are watching all bug changes.

[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.

https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #12 from Andreas Grois --- I think the MR is done for now. I've modified the Demo, Example and Templates to compile with the immutable API, modified the tutorial and readme and written a changelog. While working on the Demo I found an