revset: stop serializing node when using "%ln" Turning hundred of thousand of node from node to hex and back can be slow… what about we stop doing it? In many case were we are using node id we should be using revision id. However this is not a good reason to have a stupidly slow implementation of "%ln". This caught my attention again because the phase discovery during push make an extensive use of "%ln" or huge set. In absolute, that phase discovery probably should use "%ld" and need to improves its algorithmic complexity, but improving "%ln" seems simple and long overdue. This greatly speeds up `hg push` on repository with many drafts. Here are some relevant poulpe benchmarks: ### data-env-vars.name = mozilla-try-2023-03-22-zstd-sparse-revlog # benchmark.name = hg.command.push # bin-env-vars.hg.flavor = default # bin-env-vars.hg.py-re2-module = default # benchmark.variants.explicit-rev = all-out-heads # benchmark.variants.issue6528 = disabled # benchmark.variants.protocol = ssh # benchmark.variants.reuse-external-delta-parent = default ## benchmark.variants.revs = any-1-extra-rev before: 44.235070 after: 20.416329 (-53.85%, -23.82) ## benchmark.variants.revs = any-100-extra-rev before: 49.234697 after: 26.519829 (-46.14%, -22.71) ### benchmark.name = hg.command.bundle # bin-env-vars.hg.flavor = default # bin-env-vars.hg.py-re2-module = default # benchmark.variants.revs = all # benchmark.variants.type = none-streamv2 ## data-env-vars.name = heptapod-public-2024-03-25-zstd-sparse-revlog before: 10.138396 after: 7.750458 (-23.55%, -2.39) ## data-env-vars.name = mercurial-public-2024-03-22-zstd-sparse-revlog before: 1.263859 after: 0.700229 (-44.60%, -0.56) ## data-env-vars.name = mozilla-try-2023-03-22-zstd-sparse-revlog before: 399.484481 after: 346.5089 (-13.26%, -52.98) ## data-env-vars.name = pypy-2024-03-22-zstd-sparse-revlog before: 4.540080 after: 3.401700 (-25.07%, -1.14) ## data-env-vars.name = tryton-public-2024-03-22-zstd-sparse-revlog before: 2.975765 after: 1.870798 (-37.13%, -1.10)

     1

  $ hg init repo

     2

  $ cd repo

     3

  $ echo This is file a1 > a

     4

  $ echo This is file b1 > b

     5

  $ hg add a b

     6

  $ hg commit -m "commit #0"

     7

  $ echo This is file b22 > b

     8

  $ hg commit -m "comment #1"

     9

  $ hg update 0

    10

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    11

  $ rm b

    12

  $ hg commit -A -m "comment #2"

    13

  removing b

    14

  created new head

    15

  $ hg update 1

    16

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    17

  $ rm b

    18

  $ hg update -c 2

    19

  abort: uncommitted changes

    20

  [20]

    21

  $ hg revert b

    22

  $ hg update -c 2

    23

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

    24

  $ mv a c

    25

    26

Should abort:

    27

    28

  $ hg update 1

    29

  abort: uncommitted changes

    30

  (commit or update --clean to discard changes)

    31

  [255]

    32

  $ mv c a

    33

    34

Should succeed:

    35

    36

  $ hg update 1

    37

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved