-
Notifications
You must be signed in to change notification settings - Fork 316
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
[Handle] Use get_optional
instead of get_value<double>
#2061
base: master
Are you sure you want to change the base?
[Handle] Use get_optional
instead of get_value<double>
#2061
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2061 +/- ##
==========================================
- Coverage 89.40% 89.35% -0.06%
==========================================
Files 139 139
Lines 14975 14978 +3
Branches 1281 1287 +6
==========================================
- Hits 13389 13383 -6
+ Misses 1107 1105 -2
- Partials 479 490 +11
Flags with carried forward coverage won't be shown. Click here to find out more.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like.
If we don't merge this, we should apply the changes from f958dfe also to the master.
@saikishor @christophfroehlich , just for my knowledge, could you provide some context and outline a few discussion points ? 🙇 |
and here the origin of the API discussions |
basically, |
After some discussion with @christophfroehlich we thought
get_optional
might make more sense and explicit compared toget_value<double>
and again get its value with.value()