As noted in initial review of MissingAncestors, adding
NULL_REVISION in constructor in case the given bases is
empty wasn't really useful, yet it's been kept for identity
with the Python implementation
Details
Details
- Reviewers
kevincox - Group Reviewers
hg-reviewers - Commits
- rHG977432970080: rust: stop putting NULL_REVISION in MissingAncestors.bases
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
rust/hg-core/src/ancestors.rs | ||
---|---|---|
245 | I think it would be more clear if you filtered the NULL_REVISION out before extending the set. let new_bases = new_bases.into_iter().filter(|&rev| rev != NULL_REVISION); self.bases.extend(new_bases); |
I think it would be more clear if you filtered the NULL_REVISION out before extending the set.