but i think i'll put that off until we have a design for better API-specific properties
but 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
Pidk whatever
Ppoint is it's cool
D
Dhonestly the JIT diasm of the load methods is horrible right now
P
Dso that makes me super happy
P
D
PWHY DO YOU HAVE SO MANY BLOBS
DI have so many blob
D
Ddue to the large amount of branches I've created in the last couple of days in the Silk repo git has slowed down to a painful amount....
DNow there are!
Dwhat
Dwhere