<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Binary Data on Nalar</title>
    <link>https://nalar.dev/tags/binary-data/</link>
    <description>Recent content in Binary Data on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/binary-data/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Python memoryview: Zero-Copy Access to Binary Buffers</title>
      <link>https://nalar.dev/python-memoryview-zero-copy-access-to-binary-buffers/</link>
      <pubDate>Wed, 02 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/python-memoryview-zero-copy-access-to-binary-buffers/</guid>
      <description>&lt;p&gt;Binary-processing code often needs only a small region of a larger byte buffer. A normal &lt;code&gt;bytes&lt;/code&gt; or &lt;code&gt;bytearray&lt;/code&gt; slice is convenient, but it creates a new object containing copied data. When buffers are large or slicing happens repeatedly on a hot path, those copies can become unnecessary allocation and memory traffic.&lt;/p&gt;&#xA;&lt;p&gt;Python&amp;rsquo;s &lt;code&gt;memoryview&lt;/code&gt; provides a different model. It exposes data from an object that supports the buffer protocol and lets Python code work with that data without first copying it into a new bytes object.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
