moonbit-refactoring

To refactor MoonBit code safely, apply incremental changes while preserving behavior and public API contracts. You should review package structure, move behavior onto owning types, and keep tests green throughout the process.

API minimization in MoonBit involves reducing the public surface area to only what callers need. This improves maintainability by applying small, safe changes within package boundaries and verifying with moon check and moon test.

Converting free functions to methods in MoonBit requires moving behavior onto owning types incrementally. You must keep changes within package boundaries, update tests and docs in the same patch, and run moon check and moon test to verify.

MoonBit refactoring requires updating docs and tests in the same patch to prevent regressions. You must run moon check and moon test after each change to ensure the refactored package maintains green tests and correct behavior.

You should split large MoonBit files and packages when maintaining complex modules, but changes must stay within package boundaries. Limitations include ensuring tests remain green and public contracts are preserved during the incremental split.

Yes, this MoonBit refactoring workflow applies to package maintenance by guiding small, safe changes. It requires reviewing package structure and using moon check and moon test after each change to verify behavior preservation.