From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Minor bug(s) with NO_MULTI_FUNC_DEF
Date: Thu, 2 Jun 2022 08:23:52 -0700 [thread overview]
Message-ID: <CAH+w=7Z7aa7fnQBjLCuQiXRn6cMzgFZ1qZowk8Hw5ORNg7boWg@mail.gmail.com> (raw)
In-Reply-To: <20220602102309.GF28173@tarpaulin.shahaf.local2>
On Thu, Jun 2, 2022 at 3:47 AM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Devil's advocate: letting this syntax bypass the NO_MULTI_FUNC_DEF check
> would break the invariant that «foo bar baz qux» and «foo {bar,baz} qux»
> are always equivalent.
We're not considering «foo {bar,baz} qux» here, rather
«foo{bar,baz}qux» (the spacing is important). The latter results in
«foobarqux foobazqux».
> So, if we document it, I'd rather it were documented as "This may change
> in the future" than as a feature.
I don't have an opinion about that, but as long as the check is done
by counting parser words it's not going to change.
prev parent reply other threads:[~2022-06-02 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 20:31 Bart Schaefer
2022-05-31 9:03 ` Peter Stephenson
2022-05-31 17:07 ` Bart Schaefer
2022-05-31 17:14 ` Bart Schaefer
2022-06-06 8:45 ` Peter Stephenson
2022-06-06 15:53 ` Peter Stephenson
2022-06-02 10:23 ` Daniel Shahaf
2022-06-02 15:23 ` Bart Schaefer [this message]
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='CAH+w=7Z7aa7fnQBjLCuQiXRn6cMzgFZ1qZowk8Hw5ORNg7boWg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--cc=zsh-workers@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).