feat: add math/base/special/minf

[gunjjoshi]

Description

What is the purpose of this pull request?

This pull request:

• adds math/base/special/minf, which would be the single-precision variant for math/base/special/min.

float stdlib_base_minf( const float x, const float y );

Related Issues

Does this pull request have any related issues?

This pull request:

• resolves a part of [RFC]: Add C implementations to base special math functions (tracking issue) #649.

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

---

@stdlib-js/reviewers

[kgryte]

LGTM. Two things to note, @gunjjoshi:

1. In general, we've moved away from test description messages like returns -0 and use the convention returns expected value. The rationale is that we'll eventually have our own in-house test runner which will provide a default error message. By standardizing around returns expected value (where appropriate), we'll make the migration process a bit easier.
2. I refactored the benchmarks to pull values from a preallocated array, rather than generating them from within the loop. The rationale is that generating random values in the loop conflates value generation with the implementation being benchmarked. Ideally, our benchmark performance should be solely due to aspects of the implementation, not the PRNG. Going forward, it would be good to write benchmarks accordingly. Especially here, the observed performance is dominated by random value generation and not the actual implementation. We want to avoid this.

[gunjjoshi]

Thanks for clarifying this @kgryte! I'll be following these conventions from now on, and will update other open PRs accordingly.