From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17013 invoked from network); 9 Jul 2021 14:57:14 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 9 Jul 2021 14:57:14 -0000 Received: from 5ess.inri.net ([107.191.111.177]) by 1ess; Fri Jul 9 10:52:17 -0400 2021 Received: from [127.0.0.1] ([104.59.85.219]) by 5ess; Fri Jul 9 10:37:05 -0400 2021 Date: Fri, 09 Jul 2021 10:37:04 -0400 From: Stanley Lieber To: 9front@9front.org In-Reply-To: References: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: core CMS dependency interface Subject: Re: [9front] Re: commit 2f8a59f4b5bfe028c022855acc19666d69eed909 Reply-To: 9front@9front.org Precedence: bulk On July 9, 2021 3:48:39 AM EDT, Anthony Martin wrote: >> rc: add subshell-function syntax >> >> fn foo @{bar} is now equivalent to >> fn foo {@{bar}}=2E As a side effect, >> this disallows creating functions >> named after keywords without first >> quoting them=2E > >Respectfully, this is just wrong=2E @ is a >unary operator=2E Repurposing it to define >a new special kind of function is a bit >much=2E > >What does this buy you over being explicit >at the call site? > > fn foo { bar } > > @foo > >One color of function is enough=2E 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=2E But is it worth the backwards >incompatibility? > >Thanks, > Anthony > if we're introducing breaking changes to important programs like the shell= , can we please at least post a warning on the mailing list? (the mailing list itself relies on she'll scripts=2E) sl