public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/18175] gdb.parse_and_eval should un-lazy results
Date: Mon, 06 Jun 2022 23:30:48 +0000 [thread overview]
Message-ID: <bug-18175-4717-1W97UMZiL1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18175-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18175
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
This came up in bug #16820, but I'm inclined to disagree.
Un-lazying by default means that if parse_and_eval reads a huge
array, it will all be copied in. But that neglects the scenario
where the code immediately uses the value to fetch just one element --
where remaining lazy would be valuable.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2022-06-06 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 21:52 [Bug python/18175] New: " xdje42 at gmail dot com
2022-06-06 23:30 ` tromey at sourceware dot org [this message]
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=bug-18175-4717-1W97UMZiL1@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).