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
Specifically, as described in cppreference. A minor change such as typedefing the container's value_type already allows the usage of std::back_inserter.
As an example of such usage, here's a use case of mine - calling a function requiring an OutputIterator as argument:
I'm not sure if making types like jlcxx::Array closer to STL-like spec is in the horizon, seeing one could just leverage the already in-place STL capabilities and just using jlcxx::apply_stl<T>(). Nonetheless, it would make usage more practical.
Addendum: Albeit slightly unrelated, I think this issue pairs nicely with #58.
The text was updated successfully, but these errors were encountered:
Specifically, as described in cppreference. A minor change such as
typedef
ing the container'svalue_type
already allows the usage ofstd::back_inserter
.As an example of such usage, here's a use case of mine - calling a function requiring an
OutputIterator
as argument:Otherwise, I'd probably need to do something like the following (if I still want to return a julia array, i.e.
jlcxx::Array
):EDIT: Assuming the following definition:
I'm not sure if making types like
jlcxx::Array
closer to STL-like spec is in the horizon, seeing one could just leverage the already in-place STL capabilities and just usingjlcxx::apply_stl<T>()
. Nonetheless, it would make usage more practical.Addendum: Albeit slightly unrelated, I think this issue pairs nicely with #58.
The text was updated successfully, but these errors were encountered: