you can wait ONE YEAR beyley i've been waiting like 15 for better generics
you can wait ONE YEAR beyley i've been waiting like 15 for better generics
Lme when my rust target folder is 6gb for hello world
Atakes 5 minutes to compile
Mthat's just any rust program
Lwell i need it right now as im writing code right now that would mildly benefit safety wise from it
Atrue
MLLVM needs to spend 7 days compiling your program into nothing
Tyou're doing it wrong if you're not compiling linux kernel+llvm+clang+rust+cargo before your hello world
Linline the whole ass app into the OS
Aidk what it is with cargo and WSL2 but yeezus
i almost fell asleep trying to wait for it to finish
i almost fell asleep trying to wait for it to finish
Mwelcome to android
Lreal
Mthe source tree is THE WHOLE THING
Tsay hello to WSL IO being android-level fast
Mwonder if i can build that on github actions, it only needs like 150gb free space
Aapparently so
AWSL2 cant even handle audio properly it seems lmfao
Awhich is
annoying
annoying
Musermode -> kernelmode -> usermode -> kernelmode -> write to disk
LWSL1 was banger im mad they didnt continue with it
MAGREED
Mfire take
Awhy what was the difference
Mstill have wsl1 installed
Mit's not just a VM
LWSL1 wasnt a whole VM
Aahhh ok
Lit literally ran the linux apps
Lon windows
Anice
Mthey actually implemented part of the linux kernel on NT
Aim guessing it was too much effort for ol' mikey to continue on with it i guess
Twe can't have nice things
Lits why its called the "windows subsystem for linux"
Lsince WSL1 was a whole NT personality iirc
Mno, it couldn't go GPU acceleration for machine learning so they ditched it
Al o l
Lthey COULD have just piped D3D12 in there like they did with WSL2
A
Pi was looking into that, it's because of silly things like it having to traverse like five functions to work out that
instead of
like a sane compiler
for x in 0..3instead of
like a sane compiler
Lpeople care about money
and machine learning makes money
and machine learning makes money
Atru
Mwhat the fuck
Mat this point maybe llvm should special case rustc output
Mmind blown that rust performs at all
Lmaybe LLVM should special case rustc and just fuckign delete the users hard drive when they try to compile rust code
Pyou create the range 0..3, you call into_iter on it, you call next on the result of that, if next is some then you loop
Ayeah idk why languages seem to be devolving into range-based for loops
Acause unless you compile it properly
Athat aint gonna be faster
Pand most of LLVM's time is spent passing over loads of those functions