BitLogger Update Changes
version 1.5.1(0.11.1)
Changes
- Fix the synchronous native file backend on macOS. POSIX
openflags now come from a C stub that reads the platform's ownfcntl.hvalues, instead of hard-coded per-target numbers. - Call
openfrom C instead of through a fixed-arity foreign declaration.openis variadic, and on Apple ARM64 the variadic argument is passed on the stack, so the direct call handedmodeto the wrong place and every macOS open failed. - Fix the Windows build of the same backend: the
_writelength argument now usesInt32::reinterpret_as_uintinstead of the deprecatedInt32::to_uint. - NUL-terminate paths passed to the C file APIs.
@utf8.encodereturns exactlylength()bytes, so the previous FFI calls read past the buffer; that happened to work on Linux and failed on macOS.
Verification
moon fmt --check,moon info, and strictmoon check --target TARGET --deny-warnpassed for native, wasm, wasm-gc, and js.- Strict
moon test --target TARGET --deny-warnpassed: native 320, wasm 312, wasm-gc 230, js 312;src-async115/108/26/108. - The macOS and Windows regressions were reproduced from the 0.11.0 CI failures and re-verified by CI on this release; neither platform could be checked locally.
Notes
- This patch supersedes 0.11.0, which failed on macOS file writes and on the Windows deprecation check. The registry has no yank command, so use 0.11.1 or newer.
- The public API is unchanged from 0.11.0.