this was the start of the 3 year journey of Silk.NET's overloads. in Silk.NET 1.0 it was exactly lik
this was the start of the 3 year journey of Silk.NET's overloads.
in Silk.NET 1.0 it was exactly like that, we had a pointer, a ref, and an array overload. however this locks you into using all unsafe, all refs, or all arrays. no in between.
in 2.0 I tried an experiment to allow our users more flexibility and generate permutations of our overloads. this worked well until we brought non-Khronos bindings into the mix and things weren't as simple. we started generating too many.
it is all or nothing, and the .NET Foundation is embracing that. Silk.NET 3.0 is the start of my goal to harmonize the .NET Foundation's bindings offerings, with ClangSharp being the common denominator, TerraFX being the "completely raw" option, and Silk.NET being the "at home with C#" option. the idea being there is no sacrifice in API coverage in going between any of the mutual bindings, you just pick the style you prefer.
Silk.NET remains committed to making unsafe possible, but silk will prioritise not unsafe just as much as unsafe because unsafe is TerraFX's forte. I will explain the DSL in detail in docs (the idea is I want something simple so that we can just tell our users "want to take a ref? use an
in Silk.NET 1.0 it was exactly like that, we had a pointer, a ref, and an array overload. however this locks you into using all unsafe, all refs, or all arrays. no in between.
in 2.0 I tried an experiment to allow our users more flexibility and generate permutations of our overloads. this worked well until we brought non-Khronos bindings into the mix and things weren't as simple. we started generating too many.
it is all or nothing, and the .NET Foundation is embracing that. Silk.NET 3.0 is the start of my goal to harmonize the .NET Foundation's bindings offerings, with ClangSharp being the common denominator, TerraFX being the "completely raw" option, and Silk.NET being the "at home with C#" option. the idea being there is no sacrifice in API coverage in going between any of the mutual bindings, you just pick the style you prefer.
Silk.NET remains committed to making unsafe possible, but silk will prioritise not unsafe just as much as unsafe because unsafe is TerraFX's forte. I will explain the DSL in detail in docs (the idea is I want something simple so that we can just tell our users "want to take a ref? use an
AsPtr method on the thing you want to take a ref to"), the SDP requires docs and unless we want to ignore our approved proposals we are not allowed to ship without docs.
