Samuel Wein

It looks like it doesn't work with the more basic instantiation either. Looking at our existing codebase it looks like `wrap-instances` are only used locally, so it may be this...

> It appears to not work even in the same pxd file (though it's necessarily in a different `cdef extern from` block on account of coming from different cpp files)

> Yup.

So at least in the triply nested case ` libcpp_vector[ IteratorWrapper [ libcpp_set [ ScoreType ] ] ] assigned_scores` this fails.

> Probably only "cppclass"es can be put as template parameter. And the instantiation is already a cython "class". ` libcpp_vector[ IteratorWrapper [ libcpp_set [ String ] ] ] assigned_scores` also...

> What if you introduce (c)typedefs for now? Let me try That at least gives us a more detailed error message: `Exception: Recursion in std::vector is not implemented for other...

Not that I should have been worrying about wrapping move to begin with, but I'd imagine this can probably be triggered other ways.

I'm still seeing this issue using a version of autowrap with #124 merged, ` Traceback (most recent call last): File "/home/samuel/.local/lib/python3.9/site-packages/autowrap-0.22.8-py3.9.egg/autowrap/CodeGenerator.py", line 520, in create_wrapper_for_class pyx_code, stub_code = self._create_wrapper_for_attribute(attribute) File...

So I've just had another look at this. It's something internal to autowrap, the call_method function has been updated in ConversionProvider in b9809a3752cf75cd40a9d3a988ad734611382ae9, but it's also been updated in CodeGenerator....

I've not followed up on this. I'd be happy to hear your theory. On Sat, Jun 25, 2022 at 10:24 PM Erik Whiting ***@***.***> wrote: > Hey @poshul I was...