user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 2/7] over: get_xref3: modify rows in-place
Date: Thu,  4 Aug 2022 08:16:58 +0000	[thread overview]
Message-ID: <20220804081703.1410595-3-e@80x24.org> (raw)
In-Reply-To: <20220804081703.1410595-1-e@80x24.org>

There's no need to create two intermediate arrays when we can
modify the existing arrayref.
---
 lib/PublicInbox/Over.pm | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/lib/PublicInbox/Over.pm b/lib/PublicInbox/Over.pm
index 786f9d92..d6409b2a 100644
--- a/lib/PublicInbox/Over.pm
+++ b/lib/PublicInbox/Over.pm
@@ -273,13 +273,13 @@ SELECT ibx_id,xnum,oidbin FROM xref3 WHERE docid = ? ORDER BY ibx_id,xnum ASC
 	my $eidx_key_sth = $dbh->prepare_cached(<<'', undef, 1);
 SELECT eidx_key FROM inboxes WHERE ibx_id = ?
 
-	[ map {
-		my $r = $_;
+	for my $r (@$rows) {
 		$eidx_key_sth->execute($r->[0]);
 		my $eidx_key = $eidx_key_sth->fetchrow_array;
 		$eidx_key //= "missing://ibx_id=$r->[0]";
-		"$eidx_key:$r->[1]:".unpack('H*', $r->[2]);
-	} @$rows ];
+		$r = "$eidx_key:$r->[1]:".unpack('H*', $r->[2]);
+	}
+	$rows;
 }
 
 sub next_by_mid {

  parent reply	other threads:[~2022-08-04  8:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  8:16 [PATCH 0/7] various op/allocation golfing Eric Wong
2022-08-04  8:16 ` [PATCH 1/7] http: coerce SERVER_PORT to integer Eric Wong
2022-08-04  8:16 ` Eric Wong [this message]
2022-08-04  8:16 ` [PATCH 3/7] isearch: mset_to_artnums: avoid unnecessary ops Eric Wong
2022-08-04  8:17 ` [PATCH 4/7] lei_overview: remove pointless map {} op Eric Wong
2022-08-04  8:17 ` [PATCH 5/7] imap: ensure_slices_exist: drop needless map and array Eric Wong
2022-08-04  8:17 ` [PATCH 6/7] feed: avoid unnecessary map loop in non-over path Eric Wong
2022-08-04  8:17 ` [PATCH 7/7] view: avoid intermediate array when streaming thread Eric Wong

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://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20220804081703.1410595-3-e@80x24.org \
    --to=e@80x24.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.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).