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
This is just an idea I wanted to write down and come back to later.
Instead of impure debugMode (true) calls before using the rest of Fluture's API, maybe I could provide an alternative to forkCatch, which runs the Future in debug mode.
I dismissed this idea a while ago, because debug context collection already happens before Future interpretation. But I think the performance- and memory- intensive bits only happen during interpretation. If that's the case, this may actually be a viable option.
The benefit of getting rid of debugMode is that Fluture's modukes will be completely pure, and finally truly eligible for tree shaking. See also #343.
The text was updated successfully, but these errors were encountered:
Avaq
changed the title
Investigate alternative debug api
Investigate option for alternative debug api
Jan 3, 2021
This is just an idea I wanted to write down and come back to later.
Instead of impure
debugMode (true)
calls before using the rest of Fluture's API, maybe I could provide an alternative toforkCatch
, which runs the Future in debug mode.I dismissed this idea a while ago, because debug context collection already happens before Future interpretation. But I think the performance- and memory- intensive bits only happen during interpretation. If that's the case, this may actually be a viable option.
The benefit of getting rid of
debugMode
is that Fluture's modukes will be completely pure, and finally truly eligible for tree shaking. See also #343.The text was updated successfully, but these errors were encountered: