Yeah, I know, I added those so marshalling can see it for now. We will have to have some kind of fixer at generator level that maps varargs to something known (i.e. what old gen has).
So, my initial idea was to crawl through generatables, look at all member generatables which have Varargs, and expand them into specific methods.
So Varargs will have an:
List<Parameter>[] attachment in metadata and for each method which takes a varargs, generate an expansion method.
__arglist only works on .NET Framework on windows, so these are the option
Yeah, I know, I added those so marshalling can see it for now. We will have to have some kind of fixer at generator level that maps varargs to something known (i.e. what old gen has).
So, my initial idea was to crawl through generatables, look at all member generatables which have Varargs, and expand them into specific methods.
So Varargs will have an:
List<Parameter>[]
attachment in metadata and for each method which takes a varargs, generate an expansion method.__arglist only works on .NET Framework on windows, so these are the option