unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Nicolas Petton <nicolas@petton.fr>
Cc: Emacs developers <emacs-devel@gnu.org>,
	Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: [PATCH] Gnu Elpa: stream.el: Add some more basic stream operations
Date: Thu, 02 Mar 2017 23:38:24 +0100	[thread overview]
Message-ID: <87efyf1ezj.fsf@drachen> (raw)
In-Reply-To: <8737evltxs.fsf@petton.fr> (Nicolas Petton's message of "Thu, 02 Mar 2017 13:55:11 +0100")

Nicolas Petton <nicolas@petton.fr> writes:

> > And this is how that looks.  WDYT?
> >
> > (defun stream-divide-with-get-rest-fun (stream get-rest-fun)
>
> Is this function public on purpose?
>
> > (defun stream-partition-with-get-rest-fun (stream get-rest-fun)
>
> Same question :)

Yes, it's public on purpose.  They have ugly names (maybe we find better
ones?), but they are useful per se as the more general tool.  I think
they are also quite nice to use, because the creation of streams is
factored out, and you can pass the essence of the calculation as a
function argument.

And `stream-divide' and `stream-partition' no doubt don't cover all use
cases one can think of.  Looking at two subsequent elements at the same
time as in `stream-divide' gives you flexibility, but the first part of
`stream-divide' will always have at least one element.  This will not
fit in some cases.

Here is another use case where I think `stream-divide-with-get-rest-fun'
suits better: I want to have the last 3 Fibonacci number less than 1000.
This is how I would do it:

#+begin_src emacs-lisp
;; -*- lexical-binding: t -*-
(let ((count 3) fibs)
  (setq fibs (stream-make (cons 1 (stream-scan #'+ 1 fibs))))
  (seq-into-sequence
   (seq-take
    (cadr
     (stream-divide-with-get-rest-fun
      fibs
      (lambda (stream)
        (let ((rest stream))
          (dotimes (_ count) (stream-pop stream))
          (while (< (stream-pop stream) 1000)
            (stream-pop rest))
          rest))))
    count)))
#+end_src

You could also do the same with `stream-divide', but it would rather
look more complicated.


Michael.



  reply	other threads:[~2017-03-02 22:38 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-02 15:42 [PATCH] Gnu Elpa: stream.el: Add some more basic stream operations Michael Heerdegen
2016-06-02 15:50 ` Michael Heerdegen
2016-06-02 19:33 ` Nicolas Petton
2016-06-02 19:44   ` Michael Heerdegen
2016-06-08 19:52   ` Michael Heerdegen
2016-06-09 11:58     ` Nicolas Petton
2016-06-09 15:06       ` Michael Heerdegen
2016-06-09 15:46         ` Nicolas Petton
2016-06-09 16:01         ` Davis Herring
2016-06-09 16:24           ` Michael Heerdegen
2016-06-09 17:11         ` Yuri Khan
2016-06-09 19:41           ` Michael Heerdegen
2016-06-09 21:06             ` Yuri Khan
2016-06-10 15:57               ` Michael Heerdegen
2016-06-10 16:13                 ` Yuri Khan
2016-06-10 19:37                   ` Michael Heerdegen
2016-09-16 23:52                   ` Michael Heerdegen
2016-09-17  6:22                     ` Yuri Khan
2016-09-25 15:38                       ` Michael Heerdegen
2016-09-25 18:41                         ` Yuri Khan
2016-09-28  1:07                           ` Michael Heerdegen
2016-09-28  4:13                             ` Yuri Khan
2016-09-28  8:50                               ` Nicolas Petton
2016-09-28 18:27                               ` Michael Heerdegen
2016-09-28 19:19                                 ` Yuri Khan
2017-03-02  2:36                                   ` Michael Heerdegen
2017-03-02  5:00                                     ` Michael Heerdegen
2017-03-02 12:58                                       ` Nicolas Petton
2017-03-02 12:55                                     ` Nicolas Petton
2017-03-02 22:38                                       ` Michael Heerdegen [this message]
2017-03-15 14:42                                         ` Michael Heerdegen
2017-03-21 11:37                                           ` Nicolas Petton
2017-03-22 17:09                                             ` Michael Heerdegen
2017-04-21  2:34                                               ` Michael Heerdegen
2017-04-22 20:34                                                 ` Nicolas Petton
2017-04-23  5:08                                                   ` Michael Heerdegen
2017-03-20 11:29                                         ` Nicolas Petton
2016-09-25 20:49                         ` John Wiegley
2016-06-12  8:34         ` Markus Triska
2016-06-12 14:07           ` Michael Heerdegen
2016-06-12 14:31             ` Nicolas Petton
2016-06-12 22:28             ` Markus Triska
2016-06-11  1:34       ` Michael Heerdegen
2016-07-06 23:20         ` Michael Heerdegen
2016-08-01 21:13           ` Michael Heerdegen
2016-08-01 22:05             ` Nicolas Petton
2016-08-02  0:39               ` Michael Heerdegen
2016-06-09 15:48 ` 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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87efyf1ezj.fsf@drachen \
    --to=michael_heerdegen@web.de \
    --cc=emacs-devel@gnu.org \
    --cc=nicolas@petton.fr \
    --cc=yuri.v.khan@gmail.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 public inbox

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

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).