Kthese tests arent == comparing the constptr
Kits doing a conversion back to string and then comparing that
Mahhhh
Pthat's just a string comparison
PthingBack is already a stringMis the conversion to string implicit or explicit
Kimplicit rn it looks like
Mshould be explicit, that's how C++ does it
Kid make it explicit personally just because of the unsafe-ty
Pimplicit for now, the idea with this is that it's magical with help of analyzers except where it is extremely dangerous
Pe.g.
string x = gl.GetString(GLEnum.Extensions) is acceptableMright that's what you want to do
Pbasically we're augmenting C# pretty heavily here to glue C# and C together, this will naturally have to include our own compile-time validation to hold our users hand
Pand when I mean augmenting C# I mean augmenting, in this MVP the
nullptr "keyword" existsMif i were making this i'd make glGetString return a special type like NullTerminatedConstPtr which is effectively the same thing but has that extra compiler metadata and that could have an implicit cast to string
Man analyzer would probably also work
Pgood food for thought though
Pi don't lie on either side of that, will have to think about it more
Pbut if one thing has come out of this conversation
Pis we NEED you for the next API review
Kaye
Mthat's fair
Pbut yeah I'm weirdly proud of
being a thing
being a thing
Plike it's completely horrible but it works
Mwhat does it do?
Pnullptr is from a global using static Silk.NET.Core.DSL; that returns a NullPtr which all pointer types can be implicitly casted fromPsounds inefficient but the JIT loves it and this is basically how C++'s nullptr works
Mit might not be a cleaner solution but i believe you can add an implicit cast from object and that will work with null
Mit just, yknow, has other problems
Pnah, it'll get confused on whether to use the
T* overload or the T[] overloadMyeah that makes sense
Mone time i was porting a java program to c# so i did fun things like
using boolean = System.Boolean;Pglobal using does make it a lot better too
Pas you only have to do it in one file now
Myeah that's the only good thing that feature introduced
Mbeing able to do using static GL everywhere
Mfinally i can remove the # from C#
PI think you're looking for TerraFX haha
Pbut no one thing I do intend on doing in 3.0 is at least offering some static methods to the people who refuse to use the API objects because "eww wtf is this OOP"
Pbut it will basically just be a wrapper over an API object for OpenGL and other bindings with weird loaders
MC++ isn't that bad you just have to deal with not knowing if your code has errors until you build it
Pyeah, I wrote C++ fulltime at work
Pfell in love with Rust in the process
Arust my beloved
Pthis is PERFECTLY NORMAL CODE
Pas much as roslyn does really complicate the codebase of generators...
P...man is it elegant
PCSharpSyntaxRewriter is actually OP
Pthere was an attempt
LPtr<void> oops