Closed RedBeard0531 closed 6 years ago
Please change to use future_value_t.
I would like value_type too but as you point out we agreed to focus on the trait style.
@LeeHowes Should the same apply to the Promise
concept?
I suppose so... let's be consistent. This is LEWG territory really I think.
Fixing this now, btw.
should be fixed; this can be closed with #106 is accepted.
Closing.
But the concept doesn't require
::value_type
. Shouldfuture_get
usefuture_value_t
or should we addSF<T>::value_type
to the concept. I personally think both would be best for consistency with other types that provide::value_type
, but it seemed like the consensus in #31 went the other way. I'd be happy to make the wording change if you tell me which way you want it to go.