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
{{ message }}
This repository was archived by the owner on Jul 26, 2023. It is now read-only.
#76 should be done first. See that issue for the rationale.
For now we'll use only a few pointers when deemed necessary and hand-craft IntPtr alternatives, but what would really be interesting is to only have to write the pointer versions and have the IntPtr overload auto-generated.
Code generation will also be needed for #55 so both issues would need the same infrastructure.
The text was updated successfully, but these errors were encountered:
AArnott
changed the title
Use pointer types everywhere and codegen an IntPtr version
Codegen IntPtr-accepting overloads of methods with native pointers
Dec 1, 2015
Code generation will also be needed for #55 so both issues would need the same infrastructure.
Just a note: #55 might be rather different from this one at least in how it's wired up. #55 may produce a separate assembly and that assembly might be in its own NuGet package as well, whereas the code gen for IntPtr would definitely produce code for the same assembly.
#76 should be done first. See that issue for the rationale.
For now we'll use only a few pointers when deemed necessary and hand-craft
IntPtr
alternatives, but what would really be interesting is to only have to write the pointer versions and have theIntPtr
overload auto-generated.Code generation will also be needed for #55 so both issues would need the same infrastructure.
The text was updated successfully, but these errors were encountered: