Issues
- 4
Link to latest proposal
#28 opened by ozra - 19
- 0
- 0
- 0
- 0
- 0
Should a specific exception be thrown when the expected<T,exception_ptr> does have a value neither an exception stored?
#14 opened by viboes - 0
Do we need a of expected<T,T>::error_or function?
#17 opened by viboes - 0
Do we need a expected<T,E>::has_error function?
#18 opened by viboes - 1
- 0
- 5
Lots of references to expected<E,T>
#24 opened by TBBle - 3
unexpect_t doesn't appear to be used
#23 opened by TBBle - 1
unexpected<E> or unexpected_type<E>
#26 opened by TBBle - 2
- 0
- 1
About expected<T, ErrorCode, Exception>
#8 opened by viboes - 1
Should expected<errc,T> and expected<exception_ptr,T> be represented by two different classes?
#11 opened by viboes - 1
Should the order of parameters be reversed expected<T,E> instead of expected<E,T>?
#16 opened by viboes - 0
Do we need an additional Traits parameter?
#19 opened by viboes - 0
- 0
Which exception throw when the user try to get the expected value but there is none?
#7 opened by viboes - 1
Update the wording for the hash support
#5 opened by viboes - 1
- 1
Update the whole doc taking in account the expected<T,E> to expected<E,T> change.
#6 opened by viboes - 0
Add wording for the relational operators
#3 opened by viboes - 0
- 0
Update the wording for swap.
#1 opened by viboes