Date: Mon, 22 Jun 2026 15:35:55 +0300
On Mon, 22 Jun 2026 at 14:19, Jan Schultke via SG16
<sg16_at_[hidden]> wrote:
> But I guess that's a bit beside the point; if there was a really large amount of data, you may approach this differently, but if there was a large amount of data, maybe you wouldn't eagerly load it all into memory either, or keep it memory-mapped, or something. This is all a bit academic.
It sounds quite non-academic to me to apply an encoding-correcting
view on a memory-mapped range and therefore apply the endian
correction
only to the parts of the range I actually end up traversing.
<sg16_at_[hidden]> wrote:
> But I guess that's a bit beside the point; if there was a really large amount of data, you may approach this differently, but if there was a large amount of data, maybe you wouldn't eagerly load it all into memory either, or keep it memory-mapped, or something. This is all a bit academic.
It sounds quite non-academic to me to apply an encoding-correcting
view on a memory-mapped range and therefore apply the endian
correction
only to the parts of the range I actually end up traversing.
Received on 2026-06-22 12:36:09