Mbecause they predate async await by like a decade
Kyup!
Monce again more shit that needs to be done by 2023 LTS or i will eat a gun
Kthere were like three projects of implementing specifically that as a standalone thing for Task<T> lmao
Kthat part is what unitask is for lmao
Kbut should really be built in
Myeah lmfao
Munitask is more optimized than what you can do yourself
Kyeah
Kits wild
Kive dug into it to learn and even mimicked a bunch of it for my velvet.async stuff
Kjust like oh this thing that is used for async locals that isnt needed right and yeets out the executioncontext and the synchronizationcontext so its even less allocation than valuetask lmao
P@shrimpcat FWIW I did overhear Fred saying that they’re investigating allocationless/struct-based yields
Masync method builders are so poorly documented i feel like i'm just guessing how this stuff works
PAh my mistake it was Cyrus, not Fred
Pgot my language designers mixed up
Phate it when that happens
P
Kunitask ironically is a good place to look to learn them lol, thats where i started. my velvet.async thing maybe also depending
GitHub
Contribute to Khitiara/Velvet.Async development by creating an account on GitHub.
Mdankedanke
Mthe fact its actually trying to implement async methods and not iterators is a bit confusing lol
Klol
Kalmost like thats what its for
Mso AwaitUnsafeOnCompleted is basically MoveNext
Ksorta, its ContinueWith(MoveNext)
Kbasically
MGist
i get paid for this shit. GitHub Gist: instantly share code, notes, and snippets.
Mthe
return default!; at the bottom is mandatory because if you use a generic AsyncMethodBuilder it always assumes its a task with a resultMwait the asyncstatemachine it generates is still a reference type 
Mi thought that was the whole point
Munless. it's a c# 10 feature.
KI think it is still a reference type because it has to work across async boundaries
Mbut there are no async boundaries because nothing is actually async because its just a generator
Kand the stack gets destroyed a whole lot
Mcould do that with a ref value type?
Mi think?
Kyeah but this is async method builder
Kthe whole infrastructure for it is built around what async needs
Kwhich is to say the state machine needs to be on the heap
Kin later c# you might get struct ones but then you end up with IAsyncStateMachineBox<T>
Mhumbug humbug
Qhey everyone, is there anything available on using silk.net within a MAUI application?
Pnope
Qthanks
Qi could only find somebody asking about this some time ago
Pyou can use Silk.NET on .NET 6+ Android and iOS, but not MAUI today
QI take it that also includes regular WPF?
Qah perfect thats good to hear
Qreally loving it so far and would like to also make a port for mobile soon
Pyeah no support for that yet, it’s all technically possible (even MAUI) but really we want to publish a package that makes it easy, we don’t want our users writing thousands of lines just to bridge their UI framework and Silk.NET
