fix 🐛 Fix bug on "gate" in gate names #8
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Previously, the debugger checked whether an instruction is a custom gate definition by testing if its text contains "gate ". Of course, this could fail if a custom gate or a register name ends with "gate".
With this pull request, we now store a set of custom gate definitions instead. Now, only the CodePreprocessor has to check for the "gate" keyword, and in this step, we have access to the tokenized code, so when we encounter the "gate" token, we can be sure it is actually a custom gate.
Checklist: