Add tickn method to redpiler JITBackend trait #170
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.
Adds a method called tickn to the redpiler JITBackend trait which executes multiple ticks per call instead of just one
While right now the overhead of going through all the abstraction layers is minimal there is still a very small overhead.
But more importantly allowing the backends to have their own implementations can allow for other backends to do specific optimizations.
For example a threaded backend could have parts of a circuit be slightly out of sync if this doesn't effect the functioning of the circuit and then sync back up at the end.
Or ticks could be skipped if no ticks are in the queue.