Remove V1 usermod#4828
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (2)
WalkthroughThis change removes the legacy usermod callback functions ( ChangesUsermod removal and rewiring
Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Suggested labels: Suggested reviewers:
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
There are several v1 usermods still in the tree -- they should get ported to v2 before we merge this. As it turns out, the v1 usermod binding is actually fully compatible with the "usermods as libraries" approach, though you can only enable one (it'll throw a linker error otherwise). |
|
How does that work then? Does the compiler just treat the CPP fille as if it's a duplicate header definition as the function is empty and magically switch to the version in the other directory if on the include path? |
|
Well blow me sideways - I wrote it months ago, but I never merged that patch! It was in my TTGO-T-Display usermod branch, PR #4600. I'd flagged it as draft as I didn't have the hardware to test it. (I have something "close enough" on my test block now; works fine, I should dust it off and submit.) But yes - that's pretty much how it works, through the power of weak symbols. The definitions in Sorry for the confusion. |
Remove legacy usermod
Summary by CodeRabbit
Refactor
Chores