From: "Mark J. Reed" <markjreed@gmail.com>
To: zsh-users@zsh.org
Subject: Re: Empty element elision and associative arrays (was Re: Slurping a file)
Date: Thu, 18 Jan 2024 11:20:13 -0500 [thread overview]
Message-ID: <CAA=-s3yPyR+bofX60r1apBS1SaxE9LsXEB94uHe=Um9XPgqSJA@mail.gmail.com> (raw)
In-Reply-To: <f6e7b8c6-a0f9-4b3f-928c-ca245eda43ef@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
On Mon, Jan 15, 2024 at 2:02 AM Lawrence Velázquez <larryv@zsh.org> wrote:
> There is no "inevitable" teration order; one must be usually be chosen and
> implemented
> explicitly, which is extra complexity that many languages choose not to
> bother with.
Indeed. To be clear, several do choose to bother; examples include Python
since 3.6, Ruby since 1.9, and PHP, which all maintain their associative
data types in insertion order. (That introduces potential pitfalls in PHP,
where *all* arrays are associative; regular ones just have numeric keys,
but those can still be rearranged out of numerical order! JavaScript avoids
that pitfall by using numeric order for numeric keys while maintaining
insertion order for non-numeric ones.)
Closer to home, the KornShell keeps its associative arrays in lexical order
by key. Which is to say there is precedent for keeping things in a
specified order, but Zsh doesn't do so. Even if it were changed such that
it started to do so as of 6.0 or whatever, you'd still have to write code
to check the version and either fail ungracefully or fall back to
maintaining the order in a separate array anyway. So even in that world,
it's simpler to just do the separate ordering in the first place, yielding
code that works in any version – at least, any version with associative
arrays.
--
Mark J. Reed <markjreed@gmail.com>
[-- Attachment #2: Type: text/html, Size: 1866 bytes --]
next prev parent reply other threads:[~2024-01-18 16:24 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 19:05 more splitting travails Ray Andrews
2024-01-12 19:19 ` Bart Schaefer
2024-01-12 19:56 ` Ray Andrews
2024-01-12 20:07 ` Mark J. Reed
[not found] ` <CAA=-s3zc5a+PA7draaA=FmXtwU9K8RrHbb70HbQN8MhmuXTYrQ@mail.gmail.com>
2024-01-12 20:03 ` Fwd: " Bart Schaefer
2024-01-12 20:32 ` Ray Andrews
2024-01-12 20:50 ` Roman Perepelitsa
2024-01-13 2:12 ` Ray Andrews
2024-01-12 20:51 ` Bart Schaefer
2024-01-12 21:57 ` Mark J. Reed
2024-01-12 22:09 ` Bart Schaefer
2024-01-13 3:06 ` Ray Andrews
2024-01-13 3:36 ` Ray Andrews
2024-01-13 4:07 ` Bart Schaefer
2024-01-13 5:39 ` Roman Perepelitsa
2024-01-13 20:02 ` Slurping a file (was: more spllitting travails) Bart Schaefer
2024-01-13 20:07 ` Slurping a file Ray Andrews
2024-01-14 5:03 ` zcurses mouse delay (not Re: Slurping a file) Bart Schaefer
2024-01-14 5:35 ` Ray Andrews
2024-01-14 10:34 ` Slurping a file (was: more spllitting travails) Roman Perepelitsa
2024-01-14 10:57 ` Roman Perepelitsa
2024-01-14 15:36 ` Slurping a file Ray Andrews
2024-01-14 15:41 ` Roman Perepelitsa
2024-01-14 20:13 ` Lawrence Velázquez
2024-01-15 0:03 ` Ray Andrews
2024-01-15 0:55 ` Empty element elision and associative arrays (was Re: Slurping a file) Bart Schaefer
2024-01-15 4:09 ` Ray Andrews
2024-01-15 7:01 ` Lawrence Velázquez
2024-01-15 14:47 ` Ray Andrews
2024-01-18 16:20 ` Mark J. Reed [this message]
2024-01-18 17:22 ` Ray Andrews
2024-01-18 17:36 ` Mark J. Reed
2024-01-18 17:55 ` Ray Andrews
2024-01-18 22:34 ` Bart Schaefer
2024-01-18 23:08 ` Ray Andrews
2024-01-19 2:46 ` Bart Schaefer
2024-01-19 2:58 ` Ray Andrews
2024-01-19 10:27 ` Stephane Chazelas
2024-01-19 13:45 ` Mikael Magnusson
2024-01-19 14:37 ` Mark J. Reed
2024-01-19 14:57 ` Ray Andrews
2024-01-19 15:46 ` Mark J. Reed
2024-01-19 16:01 ` Mikael Magnusson
2024-01-19 17:15 ` Ray Andrews
2024-01-19 17:42 ` Bart Schaefer
2024-01-19 18:45 ` Ray Andrews
2024-01-14 22:09 ` Slurping a file (was: more spllitting travails) Bart Schaefer
2024-01-15 8:53 ` Roman Perepelitsa
2024-01-16 19:57 ` Bart Schaefer
2024-01-16 20:07 ` Slurping a file Ray Andrews
2024-01-16 20:14 ` Roman Perepelitsa
2024-01-16 20:38 ` Ray Andrews
2024-01-16 20:43 ` Roman Perepelitsa
2024-01-16 22:27 ` Ray Andrews
2024-01-15 2:00 ` Slurping a file (was: more spllitting travails) Bart Schaefer
2024-01-15 4:24 ` Slurping a file Ray Andrews
2024-01-15 6:56 ` Lawrence Velázquez
2024-01-15 14:37 ` Ray Andrews
2024-01-15 15:10 ` Marc Chantreux
2024-01-15 15:29 ` Mark J. Reed
2024-01-15 16:16 ` Marc Chantreux
2024-01-15 16:33 ` MUAs (was: Re: Slurping a file) zeurkous
2024-01-16 7:23 ` Slurping a file Lawrence Velázquez
2024-01-16 14:37 ` Ray Andrews
2024-01-17 3:50 ` Lawrence Velázquez
2024-01-17 5:10 ` Ray Andrews
2024-01-15 7:26 ` Slurping a file (was: more spllitting travails) Lawrence Velázquez
2024-01-15 14:48 ` Slurping a file Ray Andrews
2024-01-15 13:13 ` Slurping a file (was: more spllitting travails) Marc Chantreux
2024-02-10 20:48 ` Stephane Chazelas
2024-02-11 0:59 ` Mikael Magnusson
2024-02-11 4:49 ` Bart Schaefer
2024-02-11 5:04 ` Mikael Magnusson
2024-02-11 4:46 ` Bart Schaefer
2024-02-11 5:06 ` Mikael Magnusson
2024-02-11 7:09 ` Stephane Chazelas
2024-01-13 2:19 ` Fwd: more splitting travails Ray Andrews
2024-01-13 3:59 ` Bart Schaefer
2024-01-13 4:54 ` Ray Andrews
2024-01-13 5:51 ` Roman Perepelitsa
2024-01-13 16:40 ` Ray Andrews
2024-01-13 18:22 ` Bart Schaefer
2024-01-13 19:08 ` Ray Andrews
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='CAA=-s3yPyR+bofX60r1apBS1SaxE9LsXEB94uHe=Um9XPgqSJA@mail.gmail.com' \
--to=markjreed@gmail.com \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).