stick those in your bin/Debug directory
stick those in your bin/Debug directory
P(or just one of them)
P@maxilevi are you using netfx or corefx?
Pand what version?
Idotnet core 2.1.4
Pawesome
Iso that fixed the windowing issue
P¯\_(ツ)_/¯
Pif you did a dotnet publish they'd likely get copied
Ibut now i am getting an exception when doing any opengl calls
II am running the triangle sample thats on github
Pthat's because of 2 reasons
P1) we never finished the triangle sample
P2) the overload that turns GenBuffers(uint, uint*) into GenBuffer() always reports null
P@maxilevi latest dev builds will work https://dev.azure.com/UltzLimited/Silk.NET/_packaging?_a=feed&feed=Experimental
Pwell once it's finished its current build
Punless it's failing
Pwhich it is
Psigh
Preeee my phone is vibratinggggg
video0.mov2.37MB
Finsert vibrator joke here
Plmao
P@sirjosh.642k4 i should've answered all your questions from https://discordapp.com/channels/337627185248468993/337627185248468993/608195488541310986
Pin #announcements
Vthank you
DDProtten case sensitivity
Pthanks 
DLooking at the Lib rn, since I couldn't figure out how to use it before, it seems it's using C# 8, but not using nullable?
Pwe're using the ??= operator which i think i subconsciously started using
DI see, any plans to add Nullable support? I really like the feature, and I don't see why not just document it moving forward (such that partial coverage is there), personally I don't find it slowing down development
PSure! Make an issue for it and we'll get it in a future preview
Dgreat, might PR it, If I find some time
Pawesome 
P@Deleted User can you talk me through where you want overloads and where you want readonly members?
Pgenerally we use get-only properties
Dwhere applicable.
for example, all
for example, all
Pure functions are applicable to be readonly Members.Dhttps://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-8#readonly-members maybe this helps explaining what I mean. not only fields can be readonly now.
Poh i didn't hear about the readonly function thing
Pthat's cool
Dyep, might even yield some performance improvements
P(i also didn't hear about System.Index and System.Range, i'm quite oblivious to this stuff until ReSharper tells me about it)
P@Deleted User Index and Range won’t work on.NET Standard 2.0 right?
Dno, I think only .Net Core 3.0
PDamn so scrap that one then
DI'll try it one sec
D When we ship Preview 8, you’ll get C# 8.0 by default if you target netstandard2.1 too.DI guess that means from there on it's supported everywhere.
PWe’re stuck on NS20 for now
D? not everywhere