From: Alex Vong <alexvong1995@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Using 'λ'
Date: Mon, 15 Oct 2018 03:10:14 +0800 [thread overview]
Message-ID: <87d0scs5t5.fsf@gmail.com> (raw)
In-Reply-To: <87pnwd553k.fsf@gmail.com> (Chris Marusich's message of "Sun, 14 Oct 2018 01:01:51 -0700")
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
Chris Marusich <cmmarusich@gmail.com> writes:
> Efraim Flashner <efraim@flashner.co.il> writes:
>
>> On Sat, Oct 13, 2018 at 04:51:48PM +0800, Alex Vong wrote:
>>> Hello guix,
>>>
>>> Should we allow the use of 'λ' in guix? I think we have discussed it
>>> before, but I forget why it was rejected. Running 'rgrep' on source
>>> shows 7 uses of it. I think it is syntactically more pleasant and it
>>> encourges the use of short functions (at least for me!).
>>>
>>
>> I know it's lambda, but to me it's like the ⓒ symbol. When I need to use
>> it I have to copy-paste it from somewhere else. I'm guessing as others
>> have mentioned, if you didn't recognize the Greek letter or come in
>> knowing some lisp then it's a wierd symbol that makes it harder to read
>> the source.
>
> I agree; I think writing "lambda" is better than using the symbol. The
> symbol is cute, but writing "lambda" is less surprising.
OK. It seems many think λ is not newcomer-friendly, which is not what I
have thought about before. (Thanks for telling me!) I guess it's because
I have seen it in school physics before. But of course this is not a
compulsory subject, so it could be a wierd symbol for many.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2018-10-14 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 8:51 Using 'λ' Alex Vong
2018-10-13 11:55 ` Tobias Geerinckx-Rice
2018-10-13 12:30 ` Alex Vong
2018-10-13 17:17 ` Leo Famulari
2018-10-14 7:04 ` Efraim Flashner
2018-10-14 8:01 ` Chris Marusich
2018-10-14 19:10 ` Alex Vong [this message]
2018-10-14 19:29 ` Chris Marusich
2018-10-15 9:45 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0scs5t5.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.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.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).