Mark Hammond

Moved to bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1866337 Change performed by the [Move to Bugzilla add-on](https://addons.mozilla.org/en-US/firefox/addon/move-to-bugzilla/).

In addition to what @badboy says, the more general solution here is to use a `trait` - ie, imagine instead of `struct Button` you had `trait Button` and the foreign...

I'd love to get this in the next release if we can get CI green.

Yeah, I had to download jna-5.14.0.jar and ensure that's in my CLASSPATH. I don't quite understand why my installed Android Studio didn't come with what I needed, but here we...

To be clear, one option is to change, eg, `[bindings.swift.custom_types.Url]` to `[bindings.custom_types.Url]`? If so, I don't think that will fly for various reasons. > Add back a language key to...

I'd consider "fallible" something which returns `Result`, not `Option` - but yeah, this isn't a pattern which will work with all bindings and really isn't what could reasonably be called...

Sorry for the confusion - I meant to suggest that what I'd call fallible is indeed `Result` rather than `Option` - but didn't mean to imply `Result` wasn't supported -...

> I think the one other option would be to implement the vec growth algorithm ourselves by calling `reserve_exact()` before pushing elements. I prefer this one slightly, but I could...

Callback interfaces are less likely to get love moving forward. I was going to suggest you use an external "trait" instead, but noticed that too appears to not be supported...

callbacks are kinda soft-deprecated because "foreign traits" offer all the same capabilities with a more consistent interface. In particular, callback interfaces are passed to rust as a `Box` which makes...