fixed the test runner

0.16.0+1

test_runnger: Pass the io to the thing

0.16.0

0.16.0+0

Delete the build.zig, it slows down the compilation when added as a d…

0.16.0-dev.1424+d3e20e71b - spaces after keywords if/for/while/switch/fn and in struct declarations

0.16.0-dev.1424+3

Spaces after keywords, spaces in container declarations

0.16.0-dev.1424+d3e20e71b - error set formatting

reverts error set formatting to the way zig natively handles it:
errror{x, y, z} → error{ x, y, z }

0.16.0-dev.1424+d3e20e71b

0.16.0-dev.1424+1

Delete the build.zig, it slows down the compilation when added as a d…

0.15.0-dev.1034+bd97b6618+runner-build.zig

Delete the build.zig, it slows down the compilation when added as a d…

0.15.0-dev.1034+bd97b6618+runner

Apply changes to the test runner

0.15.0-dev.1034+bd97b6618

better default min versions for freebsd and netbsd

Without this change, by default you get a failure when trying to cross
compile for these targets.

freebsd was error: undefined symbol: __libc_start1
netbsd was warning: invalid target NetBSD libc version: 9.4.0
error: unable to build NetBSD libc shared objects: InvalidTargetLibCVersion

now they work by default

0.14.0-dev.1550+4fba7336a

crypto.pcurves.common: generalize invert() (#23039)

The Bernstein-Yang inversion code was meant to be used only with the
fields we currently use for the NIST curves.

But people copied that code and were confused that it didn't work as
expected with other field sizes.

It doesn't cost anything to make it work with other field sizes,
that may support in the future. So let's do it.
This also reduces the diff with the example zig code in fiat crypto.

Suggested by @Rexicon226 -- Thank you!

0.14.0

crypto.pcurves.common: generalize invert() (#23039)

The Bernstein-Yang inversion code was meant to be used only with the
fields we currently use for the NIST curves.

But people copied that code and were confused that it didn't work as
expected with other field sizes.

It doesn't cost anything to make it work with other field sizes,
that may support in the future. So let's do it.
This also reduces the diff with the example zig code in fiat crypto.

Suggested by @Rexicon226 -- Thank you!