Akhil Indurti 🇵🇸
@akhil.cc
I play guitar and work on Azure at Microsoft. Opinions are my own and not the views of my employer. @smasher164@hachyderm.io,
@smasher164 on twitter
@smasher164 on twitter
But then I discovered you were really nice, just sassy haha
October 24, 2025 at 10:12 AM
But then I discovered you were really nice, just sassy haha
Not much you can do there, aside from weird runtime workarounds like signals. Ideally there’s an ecosystem-wide idiom around cancellation like in C# or Go.
September 11, 2025 at 11:54 AM
Not much you can do there, aside from weird runtime workarounds like signals. Ideally there’s an ecosystem-wide idiom around cancellation like in C# or Go.
Yes. Ideally, the code had already been partitioned up into chunks so that there are reasonable yield points.
September 11, 2025 at 7:54 AM
Yes. Ideally, the code had already been partitioned up into chunks so that there are reasonable yield points.
Manually insert calls to suspend in the cpu-bound code.
September 11, 2025 at 12:36 AM
Manually insert calls to suspend in the cpu-bound code.
Tbh, I consider this a form of row polymorphism. SML# basically does this by quantifying types with record constraints, but it doesn’t provide row variables. Row variables are overrated for most use-cases anyway.
September 11, 2025 at 12:32 AM
Tbh, I consider this a form of row polymorphism. SML# basically does this by quantifying types with record constraints, but it doesn’t provide row variables. Row variables are overrated for most use-cases anyway.