Can we merge?

Thanks Niki! I don't oppose merging, but I think that without additional action it will be difficult for others to maintain the code.

It looks to me like the test 753.fq is too large. Imagine it starts failing in the future, how would you make sense of all the constraints in there? If it comes from Liquid Haskell, I'd let it stay in Liquid Haskell.

Also, two artifacts would make maintaining this code easier:

1. A small test that rehearses the changes
2. A comment explaining what the problem was with the old implementation and how the changes addresses it. The code could have it, or it could have a reference to the PR or issue where it is explained. Otherwise, I'd expect the insights to get lost in the flux of time.

ok! I will try to minimize the test!

Shall we merge?

Thanks Niki! I removed the large tests/pos/T753.fq now that there is the smaller tests/pos/T753a.fq. But please, let me know if this is not what you want. I think we could merge when CI passes.