comparison tests/test-revset2.t @ 49510:e02dcc625171

revset: handle wdir() in `roots()`

This is already handled in `heads()`, and both are needed to determine if a set
is contiguous.

I'm guessing the `0 <= p` check was to try to filter out the null revision, but
it looks like that comes through in the corner case of a new repo with no
commits.  But that was already the case, as shown by the tests.

Before (on a clone of hg):

    $ python3.8 hg perf::revset --config extensions.perf=contrib/perf.py 'roots(all())'
    ! wall 0.059301 comb 0.040000 user 0.040000 sys 0.000000 (best of 100)

After:

    $ python3.8 hg perf::revset --config extensions.perf=contrib/perf.py 'roots(all())'
    ! wall 0.059387 comb 0.060000 user 0.060000 sys 0.000000 (best of 100)

49509:946c023212b8

prepare repository that has "default" branches of multiple roots

  $ hg init namedbranch
  $ cd namedbranch

  $ echo default0 >> a
  $ hg ci -Aqm0
  $ echo default1 >> a
  $ hg ci -m1

  $ hg update -q null
  $ echo default4 >> a
  $ hg ci -Aqm4
  $ echo default5 >> a
  $ hg ci -m5

"null" revision belongs to "default" branch (issue4683)

  $ log 'branch(null)'
  0

49510:e02dcc625171

prepare repository that has "default" branches of multiple roots

  $ hg init namedbranch
  $ cd namedbranch

  $ log 'roots(.)'
  -1
  $ log 'roots(. or wdir())'
  -1
  $ log 'roots(wdir())'
  2147483647

  $ echo default0 >> a
  $ hg ci -Aqm0
  $ echo default1 >> a
  $ hg ci -m1

  $ hg update -q null
  $ echo default4 >> a
  $ hg ci -Aqm4
  $ echo default5 >> a
  $ hg ci -m5

  $ log 'roots(. or wdir())'
  5
  $ log 'roots(wdir())'
  2147483647

"null" revision belongs to "default" branch (issue4683)

  $ log 'branch(null)'
  0