You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider when bindings with libraries which are standard STL drop in replacements like for instance: EASTL, Boost... usertype_container_default is tightly dependent on std::input_iterator_tag/std::random_access_iterator_tag, but for instance EASTL has its own input_iterator_tag/random_access_iterator_tag structs.
So instead letting the user rewrite all the usertype_container and bloat his code, we can simply convert these explicit types to template type parameters.
Thanks.
The text was updated successfully, but these errors were encountered:
An input_iterator_tag_trait/random_access_iterator_tag_trait could be handy too. The problem can be fairly easily solved thought and lessen the margin of error and code bloat/redundancy.
Consider when bindings with libraries which are standard STL drop in replacements like for instance:
EASTL
,Boost
...usertype_container_default
is tightly dependent onstd::input_iterator_tag
/std::random_access_iterator_tag
, but for instanceEASTL
has its owninput_iterator_tag
/random_access_iterator_tag
structs.So instead letting the user rewrite all the
usertype_container
and bloat his code, we can simply convert these explicit types to template type parameters.Thanks.
The text was updated successfully, but these errors were encountered: