You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Consider moving objc2_foundation into the objc2 crate #39
There's a lot of places in objc2_foundation that would benefit from being able to implement From for specific Ids:
NSArray::from_vec
NSArray::into_vec
NSData::from_vec
NSDictionary::from_keys_and_objects
NSString::from_str
And so on...
Same goes for traits like Default.
But unfortunately, we can't create these implementations because Id is defined in another crate, see RFC 2451. I tried creating a helper trait FromId for this purpose, but that doesn't work either:
pubtraitFromId<T,O:Ownership>{fnfrom_id(obj:Id<T,O>) -> Self;}impl<T,O:Ownership,X:FromId<T,O>>From<Id<T,O>>forX{fnfrom(obj:Id<T,O>) -> Self{Self::from_id(obj)}}// Errors with:// note: conflicting implementation in crate `core`:// - impl<T> From<T> for T;// note: downstream crates may implement trait `FromId<_, _>` for type `Id<_, _>`
Though doing it for Default would:
// In objc2:pubtraitIdDefault:Sized{typeOwnership:Ownership;fnid_default() -> Id<Self,Self::Ownership>;}impl<T:IdDefault>DefaultforId<T,T::Ownership>{fndefault() -> Self{T::id_default()}}// In objc2_foundation:implIdDefaultforNSString{typeOwnership = <NSStringasINSObject>::Ownership;fnid_default() -> Id<Self,Self::Ownership>{
<NSStringasINSObject>::new()}}
So possible solutions:
Move objc2_foundation to objc2::foundation (under a feature flag)
Might also be relevant to move most of the implementation of objc2_exception into objc2.
It currently uses an Exception type that doesn't implement Encode and Message, and it links manually to libobjc. Of course, these could be alleviated by introducing objc2_encode and objc2_sys as dependencies of it.
But it also returns *mut Exception instead of the correct Id<Exception, Shared>, and the only way to fix that is by moving the implementation to objc2.
I think we may move the objc2_exception implementation at some point, but the objc2_foundation separation should stay; it is fundamentally separate from the objc2 crate, and having these limitations in our own crate encourages us to create helper traits (like DefaultId and such, see #41) that can be used by all downstream crates.
I asked on the forum whether this is possible, we'll see if someone comes up with something; otherwise people will just have to import FromId/IntoId and use from_id/into_id manually
Activity
madsmtm commentedon Oct 6, 2021
Might also be relevant to move most of the implementation of
objc2_exceptionintoobjc2.It currently uses an
Exceptiontype that doesn't implementEncodeandMessage, and it links manually tolibobjc. Of course, these could be alleviated by introducingobjc2_encodeandobjc2_sysas dependencies of it.But it also returns
*mut Exceptioninstead of the correctId<Exception, Shared>, and the only way to fix that is by moving the implementation toobjc2.madsmtm commentedon Oct 15, 2021
I think we may move the
objc2_exceptionimplementation at some point, but theobjc2_foundationseparation should stay; it is fundamentally separate from theobjc2crate, and having these limitations in our own crate encourages us to create helper traits (likeDefaultIdand such, see #41) that can be used by all downstream crates.madsmtm commentedon Oct 15, 2021
I asked on the forum whether this is possible, we'll see if someone comes up with something; otherwise people will just have to import
FromId/IntoIdand usefrom_id/into_idmanuallymadsmtm commentedon Oct 31, 2021
I'm not gonna move
objc2_foundation, so I'll close this issue. Whether to use the approach in #48 or #50 can be determined in the PRs themselves.