unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: name an array function
Date: Mon, 21 Nov 2016 15:01:24 +0100	[thread overview]
Message-ID: <CAMFYt2a_Ge9JYpyNrxsTzX6ytf9uhPWSxrX1ZJeero57170PUg@mail.gmail.com> (raw)
In-Reply-To: <DA445D66-DFBB-48D4-B9C5-AB5D85005EF9@bluewin.ch>

2016-11-21 11:32 GMT+01:00 Daniel Llorens <daniel.llorens@bluewin.ch>:

>
> Hello,
>
> version 2.2 of Guile will (I hope) include rank-polymorphic versions of
> array-ref, array-set! and array-for-each. What this means is that instead
> of requiring as many indices as the rank of the array, with these functions
> you can give fewer indices and get a subarray (a ‘prefix slice’). If you
> give all the indices, they behave just as the current versions.
>
> [...]

>
> What do *you* think should be the names of these functions?
>

As far as accessors are concerned, I'm not sure whether they actaully need
names. Maybe it would be better to make them applicable, and produce
"procedures with setters"?


  parent reply	other threads:[~2016-11-21 14:01 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
2016-11-21 14:01 ` Panicz Maciej Godek [this message]
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=CAMFYt2a_Ge9JYpyNrxsTzX6ytf9uhPWSxrX1ZJeero57170PUg@mail.gmail.com \
    --to=godek.maciek@gmail.com \
    --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).