`TotalOrder` trait for floating point numbers

[andrewjradcliffe]

Define an orthogonal trait which corresponds to the totalOrder predicate the IEEE 754 (2008 revision) floating point standard.

In order to maintain coherence, the bounds on TotalOrder should most likely be TotalOrder: Float (or TotalOrder: FloatCore). Without type constraints, TotalOrder could be defined on, well, anything. Though slightly ugly, one way to deal with this is to define two traits, TotalOrderCore: FloatCore and TotalOrder: Float. On the other hand, Inv has no such constraints (due to the possibility of a meaningful implementation on rational numbers). If the crate designers could weigh in on whether to introduce constraints, that would be helpful.

Resolves: issue#256

[cuviper]

Thanks!

bors r+

[bors[bot]]

Build failed:

• Test (i586)

[cuviper]

bors r+

[bors[bot]]

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here. For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

• Format
• No Std
• Test (1.31.0)
• Test (1.35.0)
• Test (1.37.0)
• Test (1.38.0)
• Test (1.44.0)
• Test (1.46.0)
• Test (1.53.0)
• Test (1.62.0)
• Test (beta)
• Test (i586)
• Test (nightly)
• Test (stable)

[TESLA-SATI]

1554 - push

• build(deps): bump num-traits from 0.2.18 to 0.2.19