core: mark float ClampBounds methods as #[inline]

[ojeda]

Commit bd174e1 ("Implement clamp_to") added a few float methods that are not marked #[inline]. This causes core to require new symbols in soft-float builds, even if the methods are unused, e.g. from the Linux kernel:

ld.lld: error: undefined symbol: fmaximum_numf
>>> referenced by core.1f440ee8661e09f9-cgu.0
>>>               rust/core.o:(<core::ops::range::RangeFrom<f32> as core::cmp::clamp::ClampBounds<f32>>::clamp) in archive vmlinux.a

(and similar for f{min,max}imum_num{f,} and __gt{s,d}f2).

It is possible to work around this in the Linux side, but these methods should probably be #[inline] to begin with, like many other similar methods are.

Thus mark them as inline.

[rustbot]

r? @clarfonthey

rustbot has assigned @clarfonthey.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

• Owners of files modified in this PR: libs
• libs expanded to 12 candidates
• Random selection from JohnTitor, Mark-Simulacrum, clarfonthey

[clarfonthey]

These things pop up in the weirdest places. I think marking these as inline is perfectly fine and if it accomplishes what you want, doubly so.

@bors r+ rollup

[rust-bors]

📌 Commit 07c0090 has been approved by clarfonthey

It is now in the queue for this repository.

[ojeda]

These things pop up in the weirdest places. I think marking these as inline is perfectly fine and if it accomplishes what you want, doubly so.

Thanks for the quick review! :)

Yeah, the kernel build works with these 3 (all needed, i.e. it is the minimum set -- maybe the other methods on top could be marked too, but they are generic anyway).