Mads Marquart

The issue is tracked upstream in https://github.com/notgull/tiny-xlib/issues/15, there's nothing actionable for `softbuffer` to do here, so I'll close this.

Indeed, that's wrong, Winit is comparing the pointer address of `MonitorHandle` itself (not the pointer address of the inner `UIScreen`). I've put up https://github.com/rust-windowing/winit/pull/4013, though don't have the time rn...

Actually, creating news methods (i.e. not overriding) is safe (provided they are not special methods like `retain`, or private underscored methods). So perhaps we need a `#[override]` attribute (that is...

Okay so we have two cases that I see a solution to: - Creating new methods: - Check that their selector is not an "unsafe" selector. - Verify that the...

Another option is to have traits for each implementation, that the user can then select. So e.g.: ```rust trait NSView_methods { fn drawRect(&self, rect: NSRect); } // Usage define_class!( struct...

Though maybe the idea of specifying which class' method you're overriding is not a bad one? It would allow us to get the type from `NSView::drawRect` directly, and maybe with...

Note that we're assuming the user uses the same method names as the superclass/protocol, which they don't necessarily have to, so we also need a way to verify that. A...

> Use Rust's trait system for this, and actually implement the methods on the trait. This would ensure that the signatures are completely equivalent. Note that this would make it...

Example run: https://github.com/madsmtm/objc2/actions/runs/5306116792/jobs/9603493154

Again in https://github.com/madsmtm/objc2/actions/runs/17418861406/job/49454331545.