Fix CI: cargo fmt and static linking on macOS

[jucasoliveira]

Fixes two CI failures. Closes #3 if applicable.

Changes

1. cargo fmt fix — src/types/inference.rs

The collect_lifetimes_from_type function had a match arm using the if-inside-block pattern, which was converted to a proper match guard. rustfmt requires the opening brace of a guarded arm to appear on a new line:

// before (fails cargo fmt --check)
Type::RefWithLifetime(id, _) | Type::MutRefWithLifetime(id, _)
    if !lifetimes.contains(id) => {
    lifetimes.push(*id);
}

// after (passes cargo fmt --check)
Type::RefWithLifetime(id, _) | Type::MutRefWithLifetime(id, _)
    if !lifetimes.contains(id) =>
{
    lifetimes.push(*id);
}

2. Static linking fix — libzstd and libunwind on macOS

Problem: The binary dynamically linked /opt/homebrew/opt/zstd/lib/libzstd.1.dylib and /opt/homebrew/opt/llvm@18/lib/libunwind.1.dylib, making the distributed artifact depend on Homebrew being installed.

Fix:

• .cargo/config.toml: replaced -L <zstd-dir> (dynamic search path) with -C link-arg=<zstd-dir>/libzstd.a (explicit static archive) for both macOS targets.
• release.yml / ci.yml macOS steps: added sudo rm -f .../libunwind*.dylib after installing LLVM@18, so the linker falls back to the system libunwind — matching the approach already used for the x86_64 cross-compile target.
• release.yml x86_64 build step: switched from -L .../zstd/lib -lzstd to the static archive path.

Test plan

• CI lint job: cargo fmt --all -- --check passes
• CI macOS test job: cargo build --release and cargo test --release pass
• Release aarch64 binary: otool -L shows no Homebrew dynamic libs
• Release x86_64 binary: otool -L shows no Homebrew dynamic libs

🤖 Generated with Claude Code