all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Petton <nicolas@petton.fr>
To: John Wiegley <johnw@newartisans.com>, emacs-devel@gnu.org
Subject: Re: [ANN] New library stream.el in ELPA
Date: Wed, 14 Oct 2015 21:31:04 +0200	[thread overview]
Message-ID: <87pp0hjlhj.fsf@petton.fr> (raw)
In-Reply-To: <m2a8rl4d57.fsf@newartisans.com>

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

John Wiegley <johnw@newartisans.com> writes:

>>>>>> Nicolas Petton <nicolas@petton.fr> writes:
>
>> stream.el is based on lazy form evaluation with memoization (which is
>> exactly what you describe IIUC), that I didn't need to expose it so I kept
>> it private to the library, see `stream--delay' and `stream-force':
>
>> https://github.com/NicolasPetton/stream/blob/master/stream.el#L62
>
> What if you expose the lower-level API, and then make lazy streaming a useful
> example. I.e., call your module "thunk.el" or "lazy.el".

What if I extract it in a thunk.el library and install it in master
(with proper tests), and have stream.el use that? (I could also put
stream.el in Emacs, but Stefan thought it would be better to have it in
ELPA).

> I would have uses for such a library beyond streams of value: for example,
> querying an external process for a tidbit of information, but abstracting this
> interaction to appear as a "value" within a thunk.

Yes, that would be really nice!

Nico

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  reply	other threads:[~2015-10-14 19:31 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 11:43 [ANN] New library stream.el in ELPA Nicolas Petton
2015-10-14 12:37 ` Michael Heerdegen
2015-10-14 13:20   ` Nicolas Petton
2015-10-14 13:33     ` Michael Heerdegen
2015-10-14 13:30   ` Nicolas Petton
2015-10-14 22:13     ` Michael Heerdegen
2015-10-15  7:38       ` Nicolas Petton
2015-10-14 16:09 ` John Wiegley
2015-10-14 16:20   ` Nicolas Petton
2015-10-14 16:40     ` John Wiegley
2015-10-14 19:31       ` Nicolas Petton [this message]
2015-10-14 21:31         ` John Wiegley
2015-10-14 21:51           ` Nicolas Petton
2015-10-15  0:42           ` raman
2015-10-15  0:48             ` John Wiegley
2015-10-18 18:29           ` Daniel Colascione
2015-10-19  4:38             ` Stephen J. Turnbull
2015-10-20  6:55               ` John Wiegley
2015-10-20  7:02                 ` Daniel Colascione
2015-10-20 15:18                   ` John Wiegley
2015-10-20 16:16                   ` Jay Belanger
2015-10-20 10:20                 ` Stephen J. Turnbull
2015-10-20 12:07             ` David Kastrup
2015-10-23 11:30           ` Nicolas Petton
2015-10-23 19:21             ` John Wiegley
2015-10-15 10:08   ` Michael Heerdegen
2015-10-15 18:25     ` John Wiegley
2015-10-15 22:13       ` Nicolas Petton
2015-10-15 20:28 ` John Mastro
2015-10-15 22:02   ` Nicolas Petton
2015-10-24 19:16 ` Michael Heerdegen
2015-10-24 20:52   ` Nicolas Petton

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=87pp0hjlhj.fsf@petton.fr \
    --to=nicolas@petton.fr \
    --cc=emacs-devel@gnu.org \
    --cc=johnw@newartisans.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.