From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Re: commit 2f8a59f4b5bfe028c022855acc19666d69eed909
Date: Fri, 27 Aug 2021 11:07:31 -0400 [thread overview]
Message-ID: <C07BF59C797BF35114F03583FCC85B76@eigenstate.org> (raw)
In-Reply-To: <YOf/V9QOmOno33rk@alice>
Quoth Anthony Martin <ality@pbrane.org>:
> > rc: add subshell-function syntax
> >
> > fn foo @{bar} is now equivalent to
> > fn foo {@{bar}}. As a side effect,
> > this disallows creating functions
> > named after keywords without first
> > quoting them.
>
> Respectfully, this is just wrong. @ is a
> unary operator. Repurposing it to define
> a new special kind of function is a bit
> much.
>
> What does this buy you over being explicit
> at the call site?
>
> fn foo { bar }
>
> @foo
>
> One color of function is enough. What's
> next?
>
> fn foo !{ bar }
>
> to mean that foo always negates the exit
> status of its body?
>
> The new quoting requirement for functions
> named after keywords seems fine, on the
> other hand. But is it worth the backwards
> incompatibility?
>
> Thanks,
> Anthony
>
After a bunch of time/thought, trying it
out, and realizing I'm not really getting
much mileage out if it:
I'm going to revert this some time next week.
next prev parent reply other threads:[~2021-08-27 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 7:48 Anthony Martin
2021-07-09 14:21 ` ori
2021-07-09 14:37 ` Stanley Lieber
2021-07-09 14:56 ` ori
2021-07-09 15:01 ` ori
2021-07-09 15:10 ` Stanley Lieber
2021-07-09 19:43 ` hiro
2021-07-09 20:44 ` hiro
2021-07-09 20:50 ` Stanley Lieber
2021-07-10 7:25 ` hiro
2021-07-10 14:16 ` Stanley Lieber
2021-08-27 15:07 ` ori [this message]
2021-09-01 19:16 ` Noam Preil
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=C07BF59C797BF35114F03583FCC85B76@eigenstate.org \
--to=ori@eigenstate.org \
--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).