[borisdevos]

Besides some refactors, there were some problems with #2 which I fixed here, in particular the unit and dual calculations. I'm surprised they didn't error previously.

Summary of the important parts:

• I added TensorKit as a weakdep, not sure if this is okay to do, but earlier versions will just behave differently.
• Iteration over the values is now row-major such that they are sorted. This was previously not the case, and not caught by the TKS testsuite because it only iterates to 10 sectors.
• Tests are reproducible, and every unitarity check is done now.
• Less allocations here and there
• size isn't hardcoded, so the first call to a sector goes through loading the Nsymbols first

Will have to revisit the readme after a package release

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines	Coverage Δ
src/bimodulesector.jl	96.68% <100.00%> (+2.34%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[lkdvos]

Why is this a weakdep? That category is typically for package extensions, which I don't think we are defining here?

[borisdevos]

This was a shot in the dark to see if this is allowed, but I want to give a compat bound to TensorKit without it being a dep, so I thought it should be a weakdep. First of all, am I allowed to compat bound a downstream package like this, and if so how should I do it? Otherwise I'll just drop it, since I explicitly mention this bound in the docs so it's at least somewhere