Olivier Gauthé

Since #1531 is not ready, would it be possible to merge this PR? Both PR make significant modifications to `GradedUnitRange` and it would be simpler for me not to deal...

Thank you @mtfishman for the review. As you noticed, there are many parts involving `UnitRangeDual` that are not satisfying. There is no good solution with the current design `UnitRangeDual

I was not doing implicit import but what your documentation calls qualified access. I realize that indeed these lines were not the correct ones as I was intending to do...

Thank you @mtfishman for the review and the summary. Concerning `TrivialSector`, I understand you want to delete it. From my perspective, I have a use case for a `TrivialSector` in...

I confirm I can execute `biber version: 2.20 (beta)`. When I try to use it in a project I run into compatibilities issues with my `biblatex` but this is unrelated....

Overall I still find there are too many kind of `UnitRange`. I wonder if we could avoid the doublet `GradedOneTo` and `GradedUnitRange`. `gradedrange` creates a `GradedOneTo`, but when slicing it...

I have no strong opinion whether there should be a `UnitRangeDual` type or not. This is mostly a design question for `BlockSparseArray`, about how much complexity you want there. In...

I realize that with the current design, there are already `GradedUnitRangeDual{

I think this is now ready for `GradedAxes`. I will focus on `BlockSparseArrays` in another PR.

Indeed slicing a `GradedUnitRangeDual` with a `Block` was an issue I spotted (this is associated with the slicing issues in ITensor/BlockSparseArrays.jl#2). Currently it yields a `LabelledUnitRange` and the dual information...