unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Linas Vepstas <linasvepstas@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: Pure (side-effect-free) calls into c/c++?
Date: Fri, 10 Jan 2020 16:36:18 -0600	[thread overview]
Message-ID: <CAHrUA357t4jtHCOxO+vMMyYZuFxtXYBPAtW8aZJ2KvNRDmBC5Q@mail.gmail.com> (raw)

So, I've got lots of C code wrapped up in guile, and I'd like to declare
many of these functions to be pure functions, side-effect-free, thus
hopefully garnering some optimizations.  Is this possible? How would I do
it? A cursory google-search reveals no clues.

To recap, I've got functions f and g that call into c++, but are pure (i.e.
always return the same value for the same arguments).   I've got
user-written code that looks like this:

(define (foo x)
    (g  (f 42) (f x) (f 43))

and from what I can tell, `f` is getting called three times whenever the
user calls `foo`. I could tell the user to re-write their code to cache,
manually: viz:

(define c42 (f 42))
(define c43 (f 43))
(define (foo x) (g c42 (f x) c43))

but asking the users to do this is .. cumbersome.  And barely worth it: `f`
takes under maybe 10 microseconds to run; so most simple-minded caching
stunts don't pay off. But since `foo` is called millions/billions of times,
I'm motivated to find something spiffy.

Ideas? suggestions?

-- Linas
-- 
cassette tapes - analog TV - film cameras - you


             reply	other threads:[~2020-01-10 22:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 22:36 Linas Vepstas [this message]
2020-01-11 14:13 ` Pure (side-effect-free) calls into c/c++? Zelphir Kaltstahl
2020-01-11 14:38 ` Matt Wette
2020-01-11 18:11   ` Linas Vepstas
2020-01-11 18:52     ` Linas Vepstas
2020-01-11 21:56       ` Taylan Kammer
2020-01-12  2:15         ` Linas Vepstas
2020-01-12  4:12         ` Linas Vepstas
2020-01-12  2:12       ` Linas Vepstas
2020-01-12  3:21         ` Taylan Kammer
2020-01-12  4:32           ` Linas Vepstas
2020-01-12  5:52             ` Linas Vepstas
2020-01-11 17:40 ` Linus Björnstam
2020-01-12  3:03   ` Christopher Lam
2020-01-12 10:35     ` Linus Björnstam

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=CAHrUA357t4jtHCOxO+vMMyYZuFxtXYBPAtW8aZJ2KvNRDmBC5Q@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --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).