Vulkan is absolutely great if you need good multithreaded rendering and low CPU overhead
Vulkan is absolutely great if you need good multithreaded rendering and low CPU overhead
AAnd learning GL on top of this made me almost die inside
I almost lost my head trying to learn GL until one day it randomly clicked and I've not looked back since
I almost lost my head trying to learn GL until one day it randomly clicked and I've not looked back since
AI agree.
Unfortunately, this is where I've hit a snag with GL
I do now need multkthreading
Not right now but I will do.
Well
Can't actually guarantee I will
Just kinda assuming with the vision I have multkthreading will very much improve performance a lot
Unfortunately, this is where I've hit a snag with GL
I do now need multkthreading
Not right now but I will do.
Well
Can't actually guarantee I will
Just kinda assuming with the vision I have multkthreading will very much improve performance a lot
Pis unsafe really that bad with OpenGL? i swear OpenGL is the only place where the overloader actually does sensible things
AUnsafe is fine now
Por does the non-unsafe stuff just have really poor visibility
Pok let me rephrase
AOh
Pis unsafe code really that unavoidable?
AWell
I don't understand in the slightest how spans work or anything like that and to be perfectly honest I don't give a monkey for them
They gave me trouble when I tried to use them so I just stuck with unsafe and it's been smooth ever since
I don't understand in the slightest how spans work or anything like that and to be perfectly honest I don't give a monkey for them
They gave me trouble when I tried to use them so I just stuck with unsafe and it's been smooth ever since
Saren't spans just collections of items?
Pa span is just both a pointer and a length
AFar as I'm aware a span is a safe pointer to an array
ABut might be wrong
PSok i understand
ATo answer your question when I tried the little amount of safe overloads I did it complained that it couldn't infer the type I was passing in
I tried for a while to fix it before I gave up and used unsafe
But I can't really say cause half the C# code I write is in an unsafe context anyway so I'm used to it now
I tried for a while to fix it before I gave up and used unsafe
But I can't really say cause half the C# code I write is in an unsafe context anyway so I'm used to it now
Si am learning C++ and i am getting the hang of pointers
Sthey are locations of other variables
Pyeah fair
Pone thing I hope 3.0 can do is, i hate to say it, but be more pythonic with its parameter types
AYeah fair enough
AI think having better safe overloads is good
A(I assume that's what you mean)
Pi.e.
PointerLike being a type that can be implicitly converted to from a pointer, array, ref(???), span, etcPno idea that'd work though
AYeah
AIf you can pull it off that would be great
Pbut yeah the worst part about today's overloader is while it gives you options, there are so many that you have literally no idea what that they are
Lits more a location in memory of 'something' not nessesary a variable
ALmao
Lit can be an IO address, an array
A600 overloads
Pnono
P6000
Pactually 12000
ALOL
Pfor a SINGLE FUNCTION
Aah yes
Rhmm
Sdarn,sololearn lied to me then
AThis function has as many overloads as the current energy prices in England
Rso did Assimp get topped?
Pyep
Swdym?
Rwoah, by what?
Pthere was a function in D2D1 with 16 pointer parameters
Roh dear god
Pgenerated 2(2^16) overloads
Roh god
Sspeaking of pointers and unsafe code,do you plan on adding a way to use safe code while creating buffer objects?
