valuesaying it can’t be passed to higher order algorithms"
pr/types. I was thinking about giving it a
stuple_detail::make_uninitializedand let functions like
drop_frontdo the placement new stuff.
hana::map< implementation_defined >but for optional it is
hana::optional<...>which makes me think it might be okay.
I'm not sure if what I am doing is a good idea yet, but I decided to not bother wrapping
tuple and just represent a
message as a tuple where some 'fields' like a payload might not be present.
BOOST_HANA_CONSTANT_ASSERT( builder::entityMessages(entity_map, access_point) == hana::make_tuple( hana::type_c<hana::tuple< hana::optional<>, channel::Upstream, action::Create, path_type, hana::optional<entity::E1>, hana::optional<> >>, hana::type_c<hana::tuple< hana::optional<bool>, channel::Downstream, action::Create, path_type, hana::optional<entity::E1>, hana::optional<> >>, ) );
There is also this, but after a second look maybe I should have used
In any case it's nbd. I'll just avoid using it that way if it remains 'implementation_defined'.
value_orbecause I wanted that map lookup to be lazy