Test: added allocations tests for types that are known to be allocation-free (SKIP THEM FOR NOW)

[franckgaga]

I choose to use the builtin @allocations macro for two reasons:

1. no additional test depedency (e.g. BechmarkTools)
2. it's faster than @ballocations in BechmarkTools

As a drawback there is known limitations (or feature? 😄) for exemple JuliaLang/julia#51112. A simple workaround for this specific issue is to create another function that calls the tested in-place function and returns nothing:

using Test
function myfunc2!(arg1, arg2)
    myfunc!(arg1, arg2)
    return nothing
end
@test @allocations(myfunc2!(arg1, arg2)) == 0

It seems to work well on Julia 1.11.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.88%. Comparing base (a8b8c9b) to head (a412fcf).
Report is 8 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #187   +/-   ##
=======================================
  Coverage   98.88%   98.88%           
=======================================
  Files          25       25           
  Lines        4205     4205           
=======================================
  Hits         4158     4158           
  Misses         47       47           

☔ 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.

[franckgaga]

Also skip pre version in CI badge with this addition in CI.yml:

continue-on-error: ${{ matrix.version == 'nightly' || matrix.version == 'pre' }}

For now the tests on the pre version does not precompile at all. I am pretty confident that it's not caused by MPC.jl, so let's remove this test from CI badge.

[franckgaga]

The tests pass if coverage=false, but fail otherwise on Julia v1.11.4. This is caused by JuliaLang/julia#49978 and JuliaLang/julia#57220

Will skip the allocations test for now with @test_skip and see how the issue evolves.