You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doing in process traces using ts lib would allow us to provide more information in an on-demand manner. For example, types.json only includes the display field when it is cheap to generate. With a live trace we could generate the displays as needed.
As a side benefit, in memory fs should reduce skew due to IO overhead during tracing.
The text was updated successfully, but these errors were encountered:
this is higher priority now as it enables much more functionality. It can't be done in process without blocking the event loop and freezing the vscode UI, so I'm working on a server we can spawn and communicate with via web sockets
Doing in process traces using ts lib would allow us to provide more information in an on-demand manner. For example, types.json only includes the display field when it is cheap to generate. With a live trace we could generate the displays as needed.
As a side benefit, in memory fs should reduce skew due to IO overhead during tracing.
The text was updated successfully, but these errors were encountered: