Fix a crash when using value(forKey:) on a LinkingObjects property #6384
Conversation
This file contains 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
Obtaining an obj-c compatible reference to LinkingObjects now requires going through the accessor rather than reading the ivar directly due to the ivar being swift struct.
tgoyne
force-pushed
the
tg/linkingobjects-valueforkey
branch
from
a5bf4cb to
d965cb0
Compare
jsflax
approved these changes
Dec 17, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Obtaining an obj-c compatible reference to LinkingObjects now requires going through the accessor rather than reading the ivar directly due to the ivar being a swift struct.
Fixes #6366.