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 4062 invoked from network); 9 Jul 2021 07:53:04 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 9 Jul 2021 07:53:04 -0000 Received: from MTA-11-3.privateemail.com ([198.54.122.105]) by 1ess; Fri Jul 9 03:48:57 -0400 2021 Received: from mta-11.privateemail.com (localhost [127.0.0.1]) by mta-11.privateemail.com (Postfix) with ESMTP id EA0BD18001F3 for <9front@9front.org>; Fri, 9 Jul 2021 03:48:47 -0400 (EDT) Received: from localhost (unknown [10.20.151.224]) by mta-11.privateemail.com (Postfix) with ESMTPA id 56C6A18001EB for <9front@9front.org>; Fri, 9 Jul 2021 03:48:47 -0400 (EDT) Date: Fri, 9 Jul 2021 00:48:39 -0700 From: Anthony Martin To: 9front@9front.org Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: ClamAV using ClamSMTP List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: generic self-healing DOM CSS-based SQL base injection optimizer Subject: [9front] Re: commit 2f8a59f4b5bfe028c022855acc19666d69eed909 Reply-To: 9front@9front.org Precedence: bulk > 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