Support both & and | for metasets

[frostming]

Fix #68

[codecov]

Codecov Report

❌ Patch coverage is 72.82609% with 25 lines in your changes missing coverage. Please review.
✅ Project coverage is 57.65%. Comparing base (4097493) to head (38472b2).

Files with missing lines	Patch %	Lines
src/passa/internals/markers.py	59.18%	13 Missing and 7 partials ⚠️
src/passa/internals/specifiers.py	76.92%	1 Missing and 2 partials ⚠️
src/passa/models/metadata.py	93.33%	0 Missing and 2 partials ⚠️

Additional details and impacted files

@@                 Coverage Diff                 @@
##           add-tests-frost      #69      +/-   ##
===================================================
+ Coverage            54.96%   57.65%   +2.69%     
===================================================
  Files                   42       42              
  Lines                 2700     2756      +56     
  Branches               475      495      +20     
===================================================
+ Hits                  1484     1589     +105     
+ Misses                1100     1027      -73     
- Partials               116      140      +24     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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

[uranusjr]

I’m cool with &, |, and bool, but not sure about the others. == could work, but I’m hesitant since it can result in false negative. I don’t get why < is needed at all, and the implementation even less.

[frostming]

== is used for deduplicating markers, false negatives(if there are any) won't do harm, while false positives will. < is a somewhat dirty hack to make sorting work, but I suspect we need sorting at all.

[uranusjr]

I would suggest using a regular function with proper docstring instead (say a.is_identical_to(b)) since == has the potential to be misused in the future. I don’t think in-class sorting makes sense here since the logic is completely arbitrary; it’s better to pass in a custom key= argument when sorting instead.