pointless otherwise as strings aren’t passed by ref so that remarshalled value is inaccessible
pointless otherwise as strings aren’t passed by ref so that remarshalled value is inaccessible
DI think something like that happens
Dneed to have a look
NHi, Kai. I'm here if you need to ask questions.
DNativeApiGenerator gives CS0208 when using ref string, it's fine with PInvoke
Dyup, there's a bunch of problems around string marshalling like this
D@Perksey please review the OpenAL thing, I want to also fix the bitdepth thing soon
Pwill do
Pjust finishing up on my stuff
Dawesome
DIdk why I always do this, start one week before the update happens, and then my list of things I want to get in grows every day
Phaha
Pi wanted to get more in too
Plike the MSAA thing for OpenGL
Didk why I commented "I'll try making an Avalonia integration for 2.4" like yesterday
Pbut i think i'll put that off until we have a design for better API-specific properties
Dthis is actually impossible lol
Dyup, will wait with the avalonia thing too. 3.0 stuffs
Pmight kick-off 3.0 dev after this
D
Pthere's still a lot of work being put into 2.x, like the freaking resharper plugin
Dyeah, I think we just need to avoid breaking things too hard with 3.0 for now
Dsince we will need merge later
Daaaaaaaaaaaaaaaaaaaaaah
Dwho did this
Pwhere's that
DSearchPathContainer
Pyeah there's nothing more elegant on NS20
Dfound it
Dit was you
D13.11.2020
Pyeah ik
Dno
Dthe
setoh right
DJIT is capable of transforming
static readonly into constantsDthis is the culprit
DI remember debugging JIT diasm logic for like a week
DI'm an idiot
Pthere's no way to communicate to a NS20 assembly that we're running on android without there being a literal way to set that in the NS20 lib from a xamarin android lib
Por was it ios
Dwait what
Pactually i think it was both
D? the set is unused
Pdon't think so
Doh "recommend setting manually"
D
Pin 3.0 we'll use operatingsystem
Pwhich is inlineable
Por jit intrinsic
D
