-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
Add flags and dead code elimination #53
Comments
@gaearon , if I understood your concerns correctly, the frustrating part is that code like the following will become more difficult to maintain with the increased number of commands in later versions.
If so, with match-js or a similar approach, I should be able to refactor the code similar to the following, though not exactly in your proposed form
where Currently, I see that To help me understand your problem correctly, could you, from a user's perspective, list some test commands that set flag(s)? In my forked repo, I will test my ideas. I hope that we can move towards a solution that you wanted. Cheers |
These flags are all internal and we don’t want to expose this code for the user. They are only useful for testing and local development of |
@gaearon , The above change deletes dead code on I will think if we could hide the flag and cut off the code on the time of building If you think the current progress is OK, I will do some tests and create a PR. |
This was in #257. |
Hacks like #52 are frustrating.
We need a system that lets us write stuff like
and eliminate all other branches on eject.
The text was updated successfully, but these errors were encountered: