Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate option for alternative debug api #456

Open
Avaq opened this issue Jan 3, 2021 · 0 comments
Open

Investigate option for alternative debug api #456

Avaq opened this issue Jan 3, 2021 · 0 comments

Comments

@Avaq
Copy link
Member

Avaq commented 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 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.

@Avaq Avaq changed the title Investigate alternative debug api Investigate option for alternative debug api Jan 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant