unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: propose deprecation of generalized-vector-*
Date: Sun, 3 Mar 2013 21:27:53 -0500	[thread overview]
Message-ID: <CA+U71=MHmuPJpfO3qbsd4bLxxH=OZBFWsDSHObChd8v7zWXVUw@mail.gmail.com> (raw)
In-Reply-To: <14C63C7B-DEA6-4C0C-AB18-17695BC5FAD3@bluewin.ch>

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

Hello again,


On Fri, Mar 1, 2013 at 4:01 AM, Daniel Llorens <daniel.llorens@bluewin.ch>wrote:

> > think this comes down to a more fundamental difference - I still don't
> think that functions should automatically map over arrays, and you do. If
> they did automatically map, then I would agree with you about array-ref,
> because then arrays wouldn't be fundamentally different types from the
> objects they contained.
>
> I actually agree here! I don't want regular scheme functions to have
> things done to them around their back, it would be another language. I can
> accept why you want array-ref to be strict. Indeed my approach tends to a
> confusion between a 2-array of 2-arrays and a 4-array. In guile-ploy you
> can see this in collapse-array ---if the verb doesn't provide an output
> shape, I make an assumption. I also banish 0-rank arrays.
>

It seems that I misunderstood you then, and I apologize. I am very excited
about the library you are proposing, and I would be happy to help in any
way I can (as long as I have time...)!

(I'm snipping the rest of your message because it needs more thought than I
can give it right now.)


> Best regards,
>
>         Daniel
>
>
Best,
Noah

[-- Attachment #2: Type: text/html, Size: 1790 bytes --]

  parent reply	other threads:[~2013-03-04  2:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.153.1351958430.10005.guile-devel@gnu.org>
2012-11-03 16:52 ` propose deprecation of generalized-vector-* Daniel Llorens
2012-11-03 21:10   ` Ludovic Courtès
2013-01-21 16:11     ` Andy Wingo
2013-01-22 14:31       ` Daniel Llorens
2013-01-22 18:31         ` Daniel Llorens
2013-01-22 20:52           ` Andy Wingo
2013-01-22 23:27             ` Daniel Llorens
2013-01-23  9:20               ` Andy Wingo
2013-01-23 14:55             ` Ludovic Courtès
2013-01-23  9:06         ` Andy Wingo
2013-01-23 12:20           ` Daniel Llorens
2013-02-18 15:55             ` Andy Wingo
2013-02-18 16:05               ` Noah Lavine
2013-02-18 16:25                 ` Mike Gran
2013-02-18 16:29                   ` Noah Lavine
2013-02-18 17:11                     ` David Pirotte
2013-02-18 17:17                       ` Mike Gran
2013-02-18 23:57                   ` Daniel Hartwig
2013-02-18 23:12               ` Problems with 'number->string' (was Re: propose deprecation of generalized-vector-*) Mark H Weaver
2013-02-21  1:13               ` propose deprecation of generalized-vector-* Daniel Llorens
2013-02-22  0:22                 ` Noah Lavine
2013-02-28 19:10                   ` Daniel Llorens
2013-03-01  2:42                     ` Noah Lavine
2013-03-01  3:46                       ` Noah Lavine
2013-03-01  9:01                       ` Daniel Llorens
2013-03-01  9:44                         ` Andy Wingo
2013-03-04  2:27                         ` Noah Lavine [this message]
2013-03-08 23:42                           ` array operations Daniel Llorens
2013-02-18 15:40           ` propose deprecation of generalized-vector-* Andy Wingo
2013-02-28 23:04 Nelson H. F. Beebe
2013-03-04 12:48 ` Aharon Robbins
     [not found] <mailman.191.1348070449.18828.guile-devel@gnu.org>
2012-09-19 17:20 ` Daniel Llorens
  -- strict thread matches above, loose matches on Subject: below --
2012-09-18 14:49 Daniel Llorens
2012-09-19 12:02 ` Peter TB Brett
2012-11-02 23:27 ` 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://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='CA+U71=MHmuPJpfO3qbsd4bLxxH=OZBFWsDSHObChd8v7zWXVUw@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=daniel.llorens@bluewin.ch \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).