From: Kristo <kristo.ilmari@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] libjson: make sure string contains only a single JSON value
Date: Mon, 18 Sep 2023 14:26:51 +0300 [thread overview]
Message-ID: <CAAJ3RaMSiwbw_LEf6AaCJiZZG8k7hDRgFQdaX8MyZQtQu2rLSw@mail.gmail.com> (raw)
In-Reply-To: <5705A85A-FF43-4547-9D82-3E3DC158F590@gmail.com>
On 8/8/23, Kristo <kristo.ilmari@gmail.com> wrote:
> On August 8, 2023 1:16:18 AM GMT+03:00, ori@eigenstate.org wrote:
>>does this use the `l.buf` that we free one line up?
>
> `buf` seems to be only used for copying literal and string values and
> therefore getting individual runes from the string should still be ok.
>
ping
next prev parent reply other threads:[~2023-09-18 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 15:29 Kristo
2023-08-07 22:16 ` ori
2023-08-08 14:44 ` [9front] " Kristo
2023-09-18 11:26 ` Kristo [this message]
2023-09-18 12:59 ` ori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAJ3RaMSiwbw_LEf6AaCJiZZG8k7hDRgFQdaX8MyZQtQu2rLSw@mail.gmail.com \
--to=kristo.ilmari@gmail.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).