Add support for Objective-C generics and NSArray #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change first adds support for declaring rust counterparts for Objective-C
classes that include generics.
Second, the change adds NSArray as a motivating example and use case.
Unfortunately, this set of changes does not compile due to lifetime constraints
not being satisfied. I am looking for guidance on how to resolve the lifetime
issues. What is the appropriate lifetime relationship to represent between
objects stored in NSArray and NSArray's lifetime captured in the PhantomData of NSArray?
How should Arc wrap them when accessing objects?