Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement the ?. operator on optionals #6

Open
joeseibel opened this issue Oct 20, 2023 · 0 comments · May be fixed by #30
Open

Implement the ?. operator on optionals #6

joeseibel opened this issue Oct 20, 2023 · 0 comments · May be fixed by #30

Comments

@joeseibel
Copy link
Contributor

It would be nice to provide the ?. operator as syntactic sugar for optional's map and flatMap. Instead of writing optionalComponent.map { component -> component.name }, we should be able to write optionalComponent?.name.

This was requested by @AaronGreenhouse.
@joeseibel joeseibel linked a pull request Feb 26, 2024 that will close this issue
Implement the optional call operator #30
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement the optional call operator osate/contract-annex
1 participant
@joeseibel