Dylan Perks
Dylan Perks
For example: ```cs public struct InstanceCreateInfo { public ApplicationInfo* PApplicationInfo; public ref ApplicationInfo PApplicationInfoRef => ... } ``` However, now that I think about it, it may be better to...
I'm pretty sure there's no good way to do this until dotnet/csharplang#1147 is in. Could compromise for Span overloads instead? cc @JakenVeina
Ref properties can't have setters.
The problem isn't that we can't convert pointers to refs, it's that the property overloads will only work one-way. For example, you won't be able to: ```cs applicationInfo.PNextRef = ref...
Could do methods, yeah.
Oh wait no because there's no guarantee that the ref will be valid without it being within a `fixed` block. `Unsafe.AsPointer` isn't safe here.
I can do just about anything with the generated APIs, so if you could propose what your idea would be in terms of the existing files (perhaps reuse the ApplicationInfo.gen.cs...
Ref properties, unfortunately, are strictly get-only. If we had ref fields, it would be easy to tackle as we'd be able to just use a union. If either of you...
If I had code I could probably fairly easily generate it, but I don't even know what the safe wrapper would look like atm.
Yeah. It's really just the ref problem I have no idea how to solve, but yeah that looks like something that I could do fairly easily (would require SilkTouch work,...