comparison mercurial/changelog.py @ 39301:5763216ba311

transaction: remember original len(repo) instead of tracking added revs (API)

It's silly to keep updating xrange(len(changelog), len(changelog) + 1) for
each added revision. Instead, let's simply remember the first revision to
be added.

The test output slightly changed as the branch cache is also warmed up by
stream clone, which seems more consistent.

.. api::

   ``tr.changes['revs']`` is replaced by ``tr.changes['origrepolen']`` which
   is the first revision number to be added.

39300:52e6171ec822

        This function exists because creating a changectx object
        just to access this is costly."""
        extra = self.read(rev)[5]
        return encoding.tolocal(extra.get("branch")), 'close' in extra

    def _addrevision(self, node, rawtext, transaction, *args, **kwargs):
        # overlay over the standard revlog._addrevision to track the new
        # revision on the transaction.
        rev = len(self)
        node = super(changelog, self)._addrevision(node, rawtext, transaction,
                                                   *args, **kwargs)
        revs = transaction.changes.get('revs')
        if revs is not None:
            if revs:
                assert revs[-1] + 1 == rev
                revs = pycompat.membershiprange(revs[0], rev + 1)
            else:
                revs = pycompat.membershiprange(rev, rev + 1)
            transaction.changes['revs'] = revs
        return node

39301:5763216ba311

        This function exists because creating a changectx object
        just to access this is costly."""
        extra = self.read(rev)[5]
        return encoding.tolocal(extra.get("branch")), 'close' in extra