kinda doubt `A => A` is common in any language, I have only seen it in rust
kinda doubt
A => A
Aand its everywhere mind you
Tregardless
Tyou can rebase
Tjust make sure to use the same DE
Z.NET 8 is like 1000x faster that GDScript & Python in some benchmarks. Even older Mono runtimes are like 10x faster than UE4.14 BluePrint runtimes. IL2CPP is about 3x faster than Mono and .NET 8 runtime is about 2x faster than IL2CPP making it only about 10% slower than VC++ if I remember correctly. Depends on CPUs of course but you can write low level game-engines in C# that would perform almost as well as C++ ones, maybe even better in some cases. You also have the advantage of Roslyn with code-generators, custom syntax compiler errors via Analyzers which can be used to create lang subsets to compile C# into GLSL, HLSL etc allowing the lang to be used in far more areas in very solid ways other lang compiler tools just don't allow for. UE4/5 tries to mimic some of the metadata features C# has in C++ as it ends up with a nightmare of code that literally can take the entire day to compile vs C# that would compile the same code in like 60 sec.
Ti know rebasing is something we want only for advanced users
Tbut
Tit's there
Cit's a type match
Twhatever
HI kinda like how this works right away
Cit's common in functional languages
KI'm fairly certain they are all fixed
Anoted
Cyou operate on types as values usually
Tframework is broken
T
Ayour code is fine
Tno option for steam gaming mode
Aive seen this but 100x longer
CIn Haskell you would see the below;
Ayeah and in python youd use a dictionary
Cyou can, but why do that
Abut the thing is that in Rust you implement it twice
Cnot really
Ayou have both OpPlus to "+" and "+" to OpPlus
Cyou implement a function that explains how to convert to and from
Cyeah I did it the shit way
Cyou can just implement the Into trait
Aits not just you its every rust project
Athe best part is when you have an external input that you have to map to a function
Athen you go from "+" to OpPlus to Plus(a, b) and then back
Cwait until you work with IO in Haskell ;)
Aso you end up with a cursed 6x duplicated chain
KNo that's intentional, the FW16 crashes with gamescope
KHence the message at the very bottom
Cyou will be fmap'ing, liftM and liftIO all the time
CI forgot mapM
Kit's weird because it seems like modifying /etc/sysctl.conf did something, because I did get less of the huge framedrop issue (then I found out somewhere about turning off the input lag reduction setting, and it works flawlessly now)
Ameanwhile chad C can do nested defines for for loops
Tme when i don't read
Tim becoming an end-user here more every day
A0 duplication, 0 perf degradation
Abut yeah its good its fast but most devs write garbage code in the end so it doesnt matter. Gaming industry kinda is the only place it does
Cfmap -> List.map but generalized to Functors
liftM f m -> Lift f into the context of a Monad m
liftIO a -> Lift a into the IO monad
liftM f m -> Lift f into the context of a Monad m
liftIO a -> Lift a into the IO monad
CHaskell is actually one of my favourite languages
APython is 64x slower than C in for loops and tbh if you stick something like a syscall in that for loop they are the same
Aso for cli scripts it makes -5 difference
HAs far as I remember it was this, is there any way I can check?
Tnvidia
