You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tighten logfwd-core to no_std + forbid(unsafe_code) #267
Depends on #Phase1a, #Phase1b, #Phase1c completing. This is the final step that locks down core.
Assignability
Needs review — the no_std migration may uncover hidden std dependencies. The get_unchecked → safe indexing change needs perf measurement. Copilot can do the mechanical parts but someone needs to verify the perf impact and handle any compilation issues.
changed the title [-]Phase 1d: Tighten logfwd-core to no_std + forbid(unsafe_code)[/-][+]Tighten logfwd-core to no_std + forbid(unsafe_code)[/+]on Mar 31, 2026
Activity
[-]Phase 1d: Tighten logfwd-core to no_std + forbid(unsafe_code)[/-][+]Tighten logfwd-core to no_std + forbid(unsafe_code)[/+]feat: logfwd-core is now #![no_std] + #![forbid(unsafe_code)] (#267)
strawgate commentedon Mar 31, 2026
Done in PR #375. logfwd-core is #![no_std] + #![forbid(unsafe_code)] + #![warn(missing_docs)].