prevent adding methods to the functions > and >=

[nsajko]

As documented, the intended way to implement > is to add a method to <. Similarly with >=. A package should never add a method to either > or >=.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.82%. Comparing base (7decc58) to head (15f0d80).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #771 +/- ##
=======================================
Coverage 89.82% 89.82% =======================================
Files 11 11 Lines 1032 1032 =======================================
Hits 927 927 Misses 105 105 

☔ View full report in Codecov by Sentry.
📢 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.

[devmotion]

Good catch! The reason for these unnecessary definitions is that up until recently x < y for Dual numbers was not equivalent with !(x >= y). I fixed this in #695 but apparently did not clean up the code.

[devmotion]

With only a single element in pred, the loop and the @eval below are not needed anymore. Can you remove them?

[nsajko]

This change decreases the unique invalidation count upon using ForwardDiff from 1504 to 784.

Instructions to reproduce this result:

• Do @snoop_invalidations using ForwardDiff before loading any other package except for SnoopCompileCore. Not even the REPL or Pkg may be loaded before ForwardDiff, because they load StyledStrings, which does some piracy, causing invalidation, thus affecting the result.

• Use nightly Julia v1.13, commit JuliaLang/julia@865b8be.

Data on each invalidation:

• before.json

• after.json