From: tomas@tuxteam.de
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: guile-user@gnu.org
Subject: Re: name an array function
Date: Thu, 15 Dec 2016 12:30:16 +0100 [thread overview]
Message-ID: <20161215113016.GA6817@tuxteam.de> (raw)
In-Reply-To: <E918C47B-665B-4F55-997D-998904B46287@bluewin.ch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Dec 15, 2016 at 12:12:58PM +0100, Daniel Llorens wrote:
>
> On 23 Nov 2016, at 21:48, David Pirotte <david@altosw.be> wrote:
[...]
> > I'd use
> >
> > array-slice-ref/set!
> > array-slice-for-each
> >
> > Unless I miss understood something :)
> >
> > Cheers,
> > David
>
> The slice/cell distinction is to be able to use the array as a list of items regardless of whether the items have rank 0 or not.
[...]
Makes sense.
[...]
> So what about this? if there's no comment in a week or so I'll take it as settled.
>
> | master (current) | meaning | proposal |
> |---------------------+----------------------------------+----------------------|
> | array-from* | look up subarray, even #0(x) | array-slice |
> | array-from | look up cell, so x and not #0(x) | array-cell-ref |
> | array-amend! | set cell | array-cell-set! |
> | array-for-each-cell | iterate over subarrays | array-slice-for-each |
My take: beautiful :)
Thanks for all the care you put into interface design!
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlhSfsgACgkQBcgs9XrR2kYWJwCZAU8ZUKogI1zAP783eazROTgB
a6EAn1c/gs9oIaL3OBbfI3av1bZe1En8
=a5lG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-12-15 11:30 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
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 [this message]
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=20161215113016.GA6817@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).