Special case navigation with force unwrap #36
Merged
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
Fixes #16 Force unwrapping during navigation _should_ just fall naturally out of the normal postfix operator combined with a basic navigation expression. Unfortunately, life isn't that simple, and it gets parsed as a custom infix operator instead. We can nudge things in the right direction by just declaring a `!.` operator, even though no such operator truly exists.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #16
Force unwrapping during navigation should just fall naturally out of
the normal postfix operator combined with a basic navigation expression.
Unfortunately, life isn't that simple, and it gets parsed as a custom
infix operator instead. We can nudge things in the right direction by
just declaring a
!.operator, even though no such operator trulyexists.