Introduce variable_value::as_optional<>() #87
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.
In some cases, optional<> types are used to specify missed input parameters in
functions. It may be the case when missed parameter has meaning 'unknown'
rather than 'default' and requires different behaviour.
Introduce convenient interface for program_options to write code as the
following:
as_optional() returns the value when stored type is T,
empty optional when variable_value is empty,
or raise bad_cast exception when stored type is other than T (as in case of
as()).
The latter case is considered as a kind of logic/runtime error since the user
is supposed to know which type he expects that the variable has.