I want clean, easy to understand code, where it is harder to make mistakes while making changes.
For the game data visualization, we need to make all instructions immutable to make tracking changes to the memory easier to collect in a single place instead of in each instruction.
Making the instructions immutable aids this, as all changes now have to happen through the memory core, which will act as central collector for the data about the reads/writes.
NOTES:
Blocked until the memory core is updated to save the statistics about the instructions, as the API of the read/writes might have to change and we want to avoid doing another big change everywhere in the codebase.
BLOCKERS:
[x] #205
[x] #207
Acceptance Criteria:
[x] All instructions have been updated to now be immutable
[x] The code is fully tested or a good explanation given why it should not or cannot be tested
As developer
I want clean, easy to understand code, where it is harder to make mistakes while making changes. For the game data visualization, we need to make all instructions immutable to make tracking changes to the memory easier to collect in a single place instead of in each instruction. Making the instructions immutable aids this, as all changes now have to happen through the memory core, which will act as central collector for the data about the reads/writes.
NOTES:
BLOCKERS:
Acceptance Criteria: