Order doesn't need to be preserved. A set is acceptable.
Details
Details
- Reviewers
dsp durin42 - Group Reviewers
hg-reviewers - Commits
- rHG32f348d741e5: sparse: use set for capturing profiles
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
Comment Actions
Looks good! Does it make sense to have a test that codifies that sorting doesn't matter? e.g. testing that two sparse profiles
a.sparse
[include] [exclude] x
b.sparse
[include] x [exclude]
yield the same result, no matter of the include order?
mercurial/sparse.py | ||
---|---|---|
96 | This can no longer happen. Will you or send a follow-up? |
mercurial/sparse.py | ||
---|---|---|
96 | Never mind, I didn't notice it expands the subprofiles and updated the profiles set in the loop, so the check is necessary. |
This can no longer happen. Will you or send a follow-up?