-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From StringBuilder to Logger #6462
Conversation
…leaner memory profile and faster run
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6462 +/- ##
============================================
- Coverage 28.59% 28.56% -0.03%
+ Complexity 14377 14373 -4
============================================
Files 2798 2798
Lines 274895 275068 +173
Branches 48630 48664 +34
============================================
- Hits 78593 78578 -15
- Misses 191669 191855 +186
- Partials 4633 4635 +2 ☔ View full report in Codecov by Sentry. |
(Mek.LOC_CT == loc) || | ||
(ProtoMek.LOC_HEAD == loc) || | ||
(ProtoMek.LOC_TORSO == loc) || | ||
!(movingUnit.isMek() && !(movingUnit.isProtoMek())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the first !
must go inside the parentheses; this new construction will evaluate to true
if the unit is a ProtoMek, but previously it would only evaluate to true
if the unit is not a Mek and not a ProtoMek.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One update needed, otherwise looks great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Using logging trace level for all this stuff instead of debug because it really is a level lower than debug what it is doing.
Kept the reasoning in the RankedPath as it is a great tool to understand what happened to select that object, but other than that, not much was changed in code.