From: tomas@tuxteam.de
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: guile-user@gnu.org
Subject: Re: name an array function
Date: Mon, 21 Nov 2016 14:56:09 +0100 [thread overview]
Message-ID: <20161121135609.GA15712@tuxteam.de> (raw)
In-Reply-To: <464A9A58-83D3-4C53-A936-BC2C83BC402C@bluewin.ch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Nov 21, 2016 at 02:42:58PM +0100, Daniel Llorens wrote:
>
> On 21 Nov 2016, at 14:24, tomas@tuxteam.de wrote:
>
> > So should "slice" prevail, it'd make sense to "invert" the star
> > (array-slice corresponding to array-from* and vice-versa)?
>
> I think it's more important to give the simpler names to the
> functions that are more commonly used. So I would keep the
> name array-slice* for the function that returns #0(a), in
> spite of logic.
I (politely) disagree: the most "commonly" used function is
already array-ref, so you would seldomly use array-from/slice
for a scalar result (the rank-0 result will be more frequent,
because there's no substitute). But hey, as I said.
> Of course, that's one reason why I don't like array-slice too much!
Understood.
> > Had I to look it up by name without any idea of what to look
> > for, I'd never come up with array-from, whereas I'd have a faint
> > chance of coming up with array-slice; that said, the most
> > ergonomic choice would still be (an extension of) array-ref et
> > al. or some close relative.
>
> Yeah, I do see your point.
Thanks
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlgy/PkACgkQBcgs9XrR2kakUQCfTVxPE7aXqyQkTYqQ6b7J1nyx
tMYAnRnSrx4airVvEs9gywUJ2MIY4jJJ
=lTwH
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-11-21 13:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 10:32 name an array function Daniel Llorens
2016-11-21 12:37 ` Stefan Israelsson Tampe
2016-11-21 12:55 ` tomas
2016-11-21 13:10 ` Daniel Llorens
2016-11-21 13:24 ` tomas
2016-11-21 13:42 ` Daniel Llorens
2016-11-21 13:56 ` tomas [this message]
2016-11-23 16:07 ` Daniel Llorens
2016-11-23 20:32 ` tomas
2016-11-23 20:48 ` David Pirotte
2016-12-15 11:12 ` Daniel Llorens
2016-12-15 11:30 ` tomas
2016-11-21 14:01 ` Panicz Maciej Godek
2016-11-21 14:38 ` Daniel Llorens
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161121135609.GA15712@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=daniel.llorens@bluewin.ch \
--cc=guile-user@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.
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).