Inlining members of Eventually and Cancellable? #5586
Description
Was looking at some trace data today, and I noticed that the traces are basically impossible when something uses them (e.g., the typechecker). This means that if anything is a bottleneck directly within an eventually { } or cancellable { }, we can't profile it effectively.
"Luckily" (quotes intentional), there are other bottlenecks that can be picked up in a trace that won't yield garbage, but eventually we'll want to inspect specific instances of, e.g, Eventually.Bind.