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

Optimise the optimisation stage by creating a new structure to represent instructions in bytecode. #18

Open
drwhut opened this issue Feb 2, 2020 · 1 comment
Labels
optimisation This code could be improved.
Milestone

Comments

@drwhut
Copy link
Owner

drwhut commented Feb 2, 2020

As of now, the optimisation stage will change every other instruction if needed every time bytecode is removed!

Instead, maybe "mark" bytecode to be removed over time, then remove the bytecode all at once at the end, changing instructions if necessary?

@drwhut drwhut added the optimisation This code could be improved. label Feb 2, 2020
@drwhut drwhut modified the milestones: v0.3.0, v0.4.0 Feb 24, 2020
@drwhut
Copy link
Owner Author

drwhut commented Feb 29, 2020

I am going to change the nature of the issue, and move it to the 0.4.0 update, for a simple reason.

In order to make the optimisation process as simple as possible, it would require representing each instruction in a nicely-formatted structure. But using that new structure would be very handy elsewhere in the code as well, e.g. code generation.

The reason I am changing the milestone is this change would not affect GUI editors in any way.

@drwhut drwhut changed the title Optimise the optimisation stage. Optimise the optimisation stage by creating a new structure to represent instructions in bytecode. Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
optimisation This code could be improved.
Projects
None yet
Development

No branches or pull requests

1 participant