unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: GNU Guile 2.1.7 released (beta)
Date: Mon, 27 Feb 2017 21:04:44 -0300	[thread overview]
Message-ID: <20170227210444.681b8e02@capac> (raw)
In-Reply-To: <87tw7kviu6.fsf@pobox.com>

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

Hi Andy,

> So!  Release blockers.
> ...

Not a blocker, at all, but I was thinking to this, wrt manipulating (very) large
vectors, arrays, lists ...

-]	repl - truncated-print

Right now I edit the installed (system repl common), and wrote a tip in Guile-CV's
manual so users can do that as well:  less then optimal :).  It would be nice to
provide an option, so users could set it 'just like that', in the repl, or as a
global config in their .guile (I did see lloda does that in his for arrays, but it's
not an obvious option to set, it is a 'sophisticated' little piece of code (for an
end-user at least)).

-]	error(s) while manipulating (very) large vectors or arrays

Unlike the above, it appears there is currently no way to have error (the procedure)
and raised exceptions in general, to use truncated-print, it would be cool to 'link'
the above option so error reports use it as well.


WDYT?
David

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2017-02-28  0:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18 10:31 GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-23 18:54 ` Andy Wingo
2017-02-23 20:04   ` Mike Gran
2017-02-23 21:06     ` Andy Wingo
2017-03-01 13:01       ` Thien-Thi Nguyen
2017-03-01 17:36         ` Andy Wingo
2017-03-02  5:50           ` Thien-Thi Nguyen
2017-02-24  0:52     ` Break-when [was GNU Guile 2.1.7 released (beta)] Matt Wette
2017-02-24 14:02   ` GNU Guile 2.1.7 released (beta) Andy Wingo
2017-02-24 17:46   ` Arne Babenhauserheide
2017-02-26 17:57     ` Andy Wingo
2017-02-27 19:32       ` Mike Gran
2017-02-27 20:30         ` Andy Wingo
2017-02-27 23:00       ` Thomas Morley
2017-02-28  8:31         ` Andy Wingo
2017-02-28  9:38           ` David Kastrup
2017-02-28 14:03             ` Andy Wingo
2017-03-05 16:54           ` Thomas Morley
2017-03-01 18:04       ` Arne Babenhauserheide
2017-02-28  0:04   ` David Pirotte [this message]
2017-02-28  1:49     ` Daniel Llorens
2017-03-02 20:54       ` David Pirotte

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=20170227210444.681b8e02@capac \
    --to=david@altosw.be \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@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).