Re: [PATCH v2 07/10] git-zlib: cast away potential constness of `next_in` pointer

From: Karthik Nayak <karthik.188@gmail.com>
Date: Jan 15, 2025, 16:17 UTC
Message-ID: <CAOLa=ZSGr6y8TE=OcyE_Rzc2sA4LLN6oC3nApsGLXsThkBea4Q@mail.gmail.com>
In-Reply-To: <20250114-b4-pks-compat-drop-uncompress2-v2-7-614a2158e34e@pks.im>

Patrick Steinhardt <ps@pks.im> writes:

> The `struct git_zstream::next_in` variable points to the input data that

s/that//

Show 6 quoted lines

> and is used in combination with `struct z_stream::next_in`. While that
> latter field is not marked as a constant in zlib, it is marked as such
> in zlib-ng. This causes a couple of compiler errors when we try to
> assign these fields to one another due to mismatching constness.
>
> Fix the issue by casting away the potential constness of `next_in`.

[snip]

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.