
Either way, for now you can workaround your issue by providing your own extension implementations for fusion::extension::category_of_implfusion::joint_view_tag, fusion::extension::has_key_implfusion::joint_view_tag and fusion::extension::at_key_implfusion::joint_view_tag, or, even better, wrap the joint_view up in another view which implements both (forward and associative) extension backends.
Thanks, but the workaround you are suggesting is not obvious to me.
Maybe you can help? I have started here :
template <>
template