Steven Sheldon

Thanks for the example @scoopr! So let's look at this part of the example: ``` rust let obj = test_utils::WrappedObject::new(); unsafe { msg_send![..., isEqual:obj]; } ``` Rust and the objc...

Current thoughts on how this could be possible: - [ ] #54: create a new string abstraction so nul-terminated strings can be passed to the runtime without us having to...

I wasn't aware of `mbox`, thanks for bringing it up @mehcode! It does look nice, but since this is a breaking change so I'd like to hold off on merging...

@application-developer-DA hmm that's a case I hadn't considered. Is this impacting your project? Do you know of any others and how widespread this is?

From a quick github search, I found this case: https://github.com/meh/cancer/blob/97829c41f0d677cf964f788b548feed38a7ffc56/src/main.rs#L62

Thanks for the heads up :) I could look into refactoring the macro to remove the need for `sel_impl!`, but if you've added it to your macro_use list, that'd just...

I never considered that someone might keep types that implement `Drop` in ivars! @quadrupleslap can you tell me more about your use case? I'm not sure how you'd plan to...

The ideal fix for this would be to make NSObjects not `Sized`; then the example code wouldn't even compile. Unfortunately, it doesn't seem that there's a way to make a...

If rust-lang/rfcs#709 were accepted, this could be resolved by marking NSObjects as `NotSized`.

The unsized types RFC was postponed as rust-lang/rfcs#813.