mirror of
https://github.com/bitsycore/compose-desktop-native.git
synced 2026-10-05 02:37:27 +00:00
Bitsy
2fb322776a
500 occurrences across 31 files: mWidth, mSurface, mCache and friends. The `f`
prefix is retired project-wide.
Scope was checked before touching anything, because a blind rename here could
have done real damage:
- VENDORED code is untouched. All 32 src/vendor trees contain ZERO f-prefixed
names (upstream Compose does not use the convention), so nothing in the
byte-for-byte copies could be caught by the pattern. check-vendor-clean and
check-vendor-drift both still pass.
- API-NEUTRAL. No f-prefixed name appears in any published .klib.api dump -
they were all private - so this changes no consumer-visible surface, and
apiCheck passes without a re-dump.
- The only matches inside quotes were string TEMPLATES ("...at $mPos",
"frames=$mFrames"), i.e. code references that had to be renamed with
everything else, not literal text.
Verified at runtime, not just by compiling: --nav3test, --backtest,
--multiwintest and --winattrtest all pass, and a Buttons screenshot still
renders.
Also corrects CLAUDE.md's Conventions section, which claimed the project used
"no f/in/v prefixes". That had not been true for a long time - the code uses v
for locals, in for parameters and k for file-level constants throughout. It now
documents what the code actually does, including that Composable parameters stay
plain because the name is part of the call-site API.