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.

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

No overload of select or operator?: for Optional<T> #6020

Open
mTvare6 opened this issue Jan 7, 2025 · 0 comments · May be fixed by #6022
Open

No overload of select or operator?: for Optional<T> #6020

mTvare6 opened this issue Jan 7, 2025 · 0 comments · May be fixed by #6022
Assignees
Labels
goal:forward looking Feature needed at a later date, not connected to a specific use case.

Comments

@mTvare6
Copy link

mTvare6 commented Jan 7, 2025

Currently the overloads select(bool condition, T ifTrue, __none_t ifFalse) select(bool condition, __none_t ifTrue, T ifFalse) don't exist if the stored value is Optional.
Technically it's possible to wrap it this way, select(true, Optional<T>(some), Optional<T>(none)); but it's not elegant.

mTvare6 added a commit to mTvare6/slang that referenced this issue Jan 7, 2025
@mTvare6 mTvare6 linked a pull request Jan 7, 2025 that will close this issue
@bmillsNV bmillsNV added the goal:forward looking Feature needed at a later date, not connected to a specific use case. label Jan 7, 2025
@bmillsNV bmillsNV added this to the Q1 2025 (Winter) milestone Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
goal:forward looking Feature needed at a later date, not connected to a specific use case.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants