public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: Damien MATTEI <Damien.Mattei@unice.fr>
Cc: kawa@sourceware.org
Subject: Re: StackOverflowError in a specialized map
Date: Sat, 25 Mar 2017 22:56:00 -0000	[thread overview]
Message-ID: <25387.1490482561@vereq.eip10.org> (raw)
In-Reply-To: Your message of "Tue, 21 Mar 2017 15:00:57 +0100."             <201703211500.57497.Damien.Mattei@unice.fr>

> From: Damien MATTEI <Damien.Mattei@unice.fr>
> Date: Tue, 21 Mar 2017 15:00:57 +0100
> 
> yes, thank you, but i try to stay in a functional programming style
> and avo= id "loop" that make code unreadable and hard to debug,

I suspect I may be misunderstanding your quest, but I don't see a
significant difference between a 'named let' and a nested function
definition (with respect to being functional programming).  Perhaps I
should have used a name 'recur' instead of 'loop' in my earlier version.

For example, if we wish to avoid named let altogether for some reason,
we could use the following variant of my earlier implementation.

(define (map/remove-nulls-1 proc . lsts)
  (define (f lsts result)
    (if (any null? lsts)
        (reverse result)
        (f (map cdr lsts)
           (let ((proc-result (apply proc
                                     (map car lsts))))
             (if (null? proc-result)
                 result
                 (cons proc-result
                       result))))))
  (f lsts '()))

Or, going another way, we could use fold:

(define (map/remove-nulls-2 proc . lsts)
  (reverse (apply fold
                  (lambda fargs
                    (let ((accum (last fargs))
                          (pargs (drop-right fargs 1)))
                      (let ((r (apply proc pargs)))
                        (if (null? r)
                            accum
                            (cons r accum)))))
                  '()
                  lsts)))

As before, I'm using some SRFI 1 procedures for convenience; they can be
avoided easily: any, fold, last, drop-right.  

Both the above versions, like the one I posted earlier, work without
problems in Kawa without needing the --full-tailcalls option (i.e., Kawa
properly detects and eliminates and simple cases of tail calls they
use).  The slight awkwardness of last/drop-right is due to the

But, as I noted before, perhaps I'm missing the main point of the
original question.

Regards,

-chaw


  parent reply	other threads:[~2017-03-25 22:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15 15:08 Damien MATTEI
2017-03-15 16:23 ` Per Bothner
2017-03-16 10:54   ` Damien MATTEI
2017-03-17 11:38     ` Damien MATTEI
2017-03-17 14:07       ` Sudarshan S Chawathe
2017-03-21 14:01         ` Damien MATTEI
2017-03-21 15:47           ` Per Bothner
2017-03-25 22:56           ` Sudarshan S Chawathe [this message]
2017-03-26  9:49             ` Damien Mattei
2017-03-26  9:55               ` Damien Mattei
2017-03-26 10:56                 ` Damien Mattei
2017-03-28  8:42             ` Damien MATTEI
2017-03-28 14:21               ` Damien MATTEI
2017-03-17 10:37   ` Damien MATTEI
2017-03-17 16:00     ` Per Bothner

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=25387.1490482561@vereq.eip10.org \
    --to=chaw@eip10.org \
    --cc=Damien.Mattei@unice.fr \
    --cc=kawa@sourceware.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).