We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I tried to make a struct with a parameter pack template type as such:
template<typename... Args> struct Foo { virtual void bar(Args... args) {} };
and I made a function that takes a specialization of this struct:
void fooFunc(Foo<int, double> b) {...}
I put it in an InfoMapper:
infoMap.put(new Info("Foo<int,double>").pointerTypes("TestType").virtualize());
and it did generate a function that takes the correct type
public native void pPackTest(@ByVal TestType b);
But failed to generate the actual .java file (TestType.java) Is there something I can do about this, or is this just a limitation of the parser?
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
You'll need to set Info.define() for it to do that.
infoMap.put(new Info("Foo<int,double>").pointerTypes("TestType").define().virtualize()); Like this? Because this also didn't work.
infoMap.put(new Info("Foo<int,double>").pointerTypes("TestType").define().virtualize());
Right, that's probably not going to work with template parameter packs... You can still define wrapper classes manually though.
No branches or pull requests
I tried to make a struct with a parameter pack template type as such:
and I made a function that takes a specialization of this struct:
void fooFunc(Foo<int, double> b) {...}
I put it in an InfoMapper:
infoMap.put(new Info("Foo<int,double>").pointerTypes("TestType").virtualize());
and it did generate a function that takes the correct type
public native void pPackTest(@ByVal TestType b);
But failed to generate the actual .java file (TestType.java)
Is there something I can do about this, or is this just a limitation of the parser?
The text was updated successfully, but these errors were encountered: