Re:Memory usage of a toy C# server and client with 500K conc...
by weberc2 on Wednesday January 30, 2019 @06:38PM
(#19040809)
That wouldn't solve the problem at all--at best I'm getting a marginally clearer error message. It doesn't help me (the programmer) remember (before runtime) that my expression is evaluating to an async function and not a sync function. Whether I get the runtime error, "invalid call to async function" or "future has no property 'status_code'" is of little consequence.
[ Parent
| on HN ]
There are no comments on this comment yet.