Repository navigation
How to import and use constants #114
Description
I'm modifying a library that uses objc. I need to import a constant NSString. I tried const* NSString and Id<NSString> but rustc warned me that these are not "FFI safe". This, however, appears to work:
// required to bring NSPasteboard into the path of the class-resolver
#[link(name = "AppKit", kind = "framework")]
extern "C" {
// NSString
static NSPasteboardURLReadingFileURLsOnlyKey: &'static Object;
}
Here is the usage:
let ns_dict = class!(NSDictionary);
let ns_number = class!(NSNumber);
let options: Id<NSDictionary<NSObject, NSObject>> = unsafe {
let obj: Id<NSObject> = msg_send![ns_number, numberWithBool: objc::runtime::YES];
msg_send![ns_dict, dictionaryWithObject:obj forKey: NSPasteboardURLReadingFileURLsOnlyKey]
};
Is this correct, safe and idiomatic?
Activity
madsmtm commentedon Jun 12, 2022
*const NSString, or even better,&'static NSString, should work, but doesn't becauseNSStringis incorrectly defined. Using&'static Objectinstead is perfect fine!For reference, the implementation should be changed to:
Not really sure about the usage code you provided though, depends on what your tolerance for UB is?
Id<T>is not safe to use directly in arguments / return ofmsg_send!, you should use&*objin the argument and wrap bothmsg_send!withId::from_retained_ptr.(Concretely, it would double-free if there was a panic between the two message sends, and may be UB depending on how Rust structs are laid out).
Happy to answer further questions!
betamos commentedon Jun 13, 2022
Thanks a ton for the swift and thorough response.
Slightly OT, but are there any resources like guidelines, docs or real-world examples either to help use the objc crate correctly, for people who are also Objective C beginners? It appears most people use this crate for Apple APIs FFI, but everyone seems to use it slightly differently. I can speak for myself and several of the Tauri contributors that we'd need to understand this better.
madsmtm commentedon Jun 13, 2022
I've been working on a few crates to improve the soundness situation, see
objc2if you're interested. They're not really ready for general audience, but I'm getting pretty close to integrating it intowinit, and will probably submit a bunch of PRs to other crates as well.In particular for this case, I've come up with a macro
msg_send_id!to help with following Cocoa's memory management rules, which I seriously always forget! (still need to do a little more work, see madsmtm/objc2#120).Case-in-point, I was wrong before, you should use
Id::from_ptr, notId::from_retained_ptr, becausenumberWithBool:anddictionaryWithObject:forKey:return autoreleased objects (concretely, your code would double-free and maybe use-after-free, both before and after my previous suggestion).madsmtm commentedon Jun 13, 2022
Just to be clear, it should be:
(At least I'm fairly certain...)
betamos commentedon Jun 13, 2022
I'm interested if it helps with soundness & readability. And I know more people who are (in Tauri). I think holding off until it's stable to avoid API churn is a good idea though, but at that point feel free to PR the repo linked above if you need testing grounds.
Yes, I was able to repro a segfault if I wrapped my FFI calls in an autoreleasepool. I think it was double-free in my case.
Thank you. It fixes the spurious segfault. Just goes to show how important it is to have a sound API, or if not possible, good docs - especially around memory management.