9 Jun
2025
9 Jun
'25
3:31 p.m.
On Mon Jun 9 15:31:20 2025 +0000, Jinoh Kang wrote:
This seems to be a *noreturn* function. You cannot return from this function implicitly or explicitly. The only option is to terminate or crash. I think this is best left as a `@ stub`. (If you still need to trace the error, at least use something like `__fastfail(-1);`.)
I didn't notice the approval, sorry. The MSDN does stat this is a noreturn though. Let's just hope that the app doesn't go haywire after a failfast.