relnotes/next

worker: stop relying on garbage collection to release memoryview

On CPython, before resizing the bytearray, all memoryviews referencing it must
be released. Before this change, we ensured that all references to them were
deleted. On CPython, this was enough to set the reference count to zero, which
results in garbage collecting and releasing them.

On PyPy, releasing the memoryviews is not necessary because they are implemented
differently. If it would be necessary however, ensuring that all references are
deleted would not be suffient because PyPy doesn’t use reference counting.

By using with statements that take care of releasing the memoryviews, we ensure
that the bytearray is resizable without relying on implementation details. So
while this doesn’t fix any observable bug, it increases compatiblity with other
and future Python implementations.

= Mercurial XXX =

== New Features ==

== Default Format Change ==

These changes affect newly created repositories (or new clones) done with
Mercurial XXX.

== New Experimental Features ==

== Bug Fixes ==

== Backwards Compatibility Changes ==

== Internal API Changes ==

== Miscellaneous ==