Bypassing the revset logic for trivial "null" queries means we can avoid to
trigger the filtering logic in some cases.
Details
Details
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
+ if specs == [b'null']:
+ return revset.baseset([nullrev])
This breaks --config revsetalias.null=<whatever>. Nobody would care, but
I don't know why we're so hard to optimize -r null query.
Comment Actions
I woudl says that changing null (like changing .) is calling for troubles and I would not worries.
optimising null is a good intermediate steps on the path to optimizing .; it also seems a possibly common request for automation.