[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: JSON/YAML/TOML/etc. parsing performance
From: |
Stefan Monnier |
Subject: |
Re: JSON/YAML/TOML/etc. parsing performance |
Date: |
Thu, 28 Sep 2017 17:27:36 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
> encoding is a superset of UTF-8. Also build_string should always be correct
> because it will generate a correct multibyte string for an UTF-8 string
> with non-ASCII characters, and a correct unibyte string for an ASCII
> string, right?
FWIW, I think that returning a unibyte string just because it doesn't
contain non-ASCII chars would be wrong. We should only build unibyte
strings if they represent a sequence of *bytes*, not when they represent
a sequence of *chars* which happens to only be ASCII.
Stefan
- Re: JSON/YAML/TOML/etc. parsing performance, (continued)
- Re: JSON/YAML/TOML/etc. parsing performance, Glenn Morris, 2017/09/18
- Re: JSON/YAML/TOML/etc. parsing performance, Eli Zaretskii, 2017/09/18
- Re: JSON/YAML/TOML/etc. parsing performance, Philipp Stephani, 2017/09/18
- Re: JSON/YAML/TOML/etc. parsing performance, Philipp Stephani, 2017/09/19
- Re: JSON/YAML/TOML/etc. parsing performance, Eli Zaretskii, 2017/09/19
- Re: JSON/YAML/TOML/etc. parsing performance, Philipp Stephani, 2017/09/28
- Re: JSON/YAML/TOML/etc. parsing performance,
Stefan Monnier <=
- Re: JSON/YAML/TOML/etc. parsing performance, Eli Zaretskii, 2017/09/29
- Re: JSON/YAML/TOML/etc. parsing performance, Philipp Stephani, 2017/09/30