We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we implicitly have FIFO order.
This should be a parameter to query and querydelete! (renamed from querypop!)
We can use types in order to have specialization:
struct FILO end struct FIFO end
The text was updated successfully, but these errors were encountered:
The hope is that using FILO order would fix the issues with EntanglementTracker
Sorry, something went wrong.
In #81 we clarified the order, but this is not implemented there.
with #106 now we support order in query, but it is pretty important to get it in querydelete! as well, @Abhishek-1Bhatt
query
querydelete!
filo
ba2tro
Successfully merging a pull request may close this issue.
Currently we implicitly have FIFO order.
This should be a parameter to query and querydelete! (renamed from querypop!)
We can use types in order to have specialization:
The text was updated successfully, but these errors were encountered: