refactor(MergedTree): take &Leader
in methods to avoid derefs #498
No reviewers
Labels
No labels
Compat/Breaking
Kind
Bad merge
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
New language
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: mergiraf/mergiraf#498
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ada4a/mergiraf:merged-tree-ref-leader"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Even though
Leader
isCopy
and dereferencing it is theoretically fine, the sheer number of places where we do so was a bit disturbing. Turns out accepting&Leader
in the methods allows removing almost all of the derefs, so I did just that.Depends on #497, since there are changes to
{print,postprocess}.rs
, which were moved/created by that PRMergedText
creation toprint
0f5f6237f7merge_postprocessor
toposprocess
b61d1c705b
to1430fd46c1