From: Alex Vong <alexvong1995@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 'package-name-version' and 'strip-store-file-name' does the same thing with different ways
Date: Sat, 20 Oct 2018 02:28:08 +0800 [thread overview]
Message-ID: <87d0s5pz9j.fsf@gmail.com> (raw)
In-Reply-To: <877eiegi2m.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 19 Oct 2018 15:52:01 +0200")
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Hello Alex,
>
> Alex Vong <alexvong1995@gmail.com> skribis:
>
>> Btw, I also noticed that the procedure 'flatten' are defined in
>> (gnu services telephony), (gnu services web) and (guix import utils).
>> [I was about to define my own version of it...]
>> I like the version using 'fold-right' together with 'match-lambda*' the
>> most. Should we move it (guix build utils) and remove the rest?
>
> About ‘flatten’ specifically, I feel like it’s not a good sign in terms
> of programming style when we end up using it (though we’d need to study
> these specific use cases), so I’m reluctant to “standardizing” it. :-)
>
Your comment lead me to find out that 'append-map' is actually what I
want. I am curious why it is an indication of bad style.
>> Similarly, 'file-sans-extension' are defined in both (guix utils) and
>> (guix build guile-build-system). They are both the same. Should we move
>> them to (guix build utils) as well?
>
> Yes, sounds like a good idea!
>
OK!
> Thanks,
> Ludo’.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2018-10-19 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 19:26 'package-name-version' and 'strip-store-file-name' does the same thing with different ways Alex Vong
2018-10-16 11:54 ` Ludovic Courtès
2018-10-16 22:04 ` Alex Vong
2018-10-19 13:52 ` Ludovic Courtès
2018-10-19 18:28 ` Alex Vong [this message]
2018-10-20 13:24 ` Ludovic Courtès
2018-10-20 8:37 ` Ricardo Wurmus
2018-10-20 13:57 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0s5pz9j.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.