From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: "René Scharfe" <l.s.r@web.de>, "Git List" <git@vger.kernel.org>
Subject: Re: [PATCH] pass constants as first argument to st_mult()
Date: Mon, 1 Aug 2016 17:11:31 -0400 [thread overview]
Message-ID: <20160801211131.6ernsu74ohod2cin@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq8twgi4qp.fsf@gitster.mtv.corp.google.com>
On Mon, Aug 01, 2016 at 02:00:46PM -0700, Junio C Hamano wrote:
> > Since multiplication is
> > commutative, it would be correct for st_mult() to just flip the order of
> > arguments it feeds to unsigned_mult_overflows().
> >
> > That may introduce the same inefficiency in other callsites, but I
> > wonder if it would be fewer.
>
> "git grep -A3 st_mult \*.c" seems to tell me that the callsites with
> a constant in their first parameter are the majority (many are
> sizeof(something)). The three places in the patch under discussion
> are the only places that got them in the different order.
Thanks for checking. I should have been less lazy and done it myself.
If the majority are the other way, I agree that just fixing the minority
is the best path forward.
> *1* I have a slight suspicion that this is cultural, i.e. how
> arithmetic is taught in grade schools. When an apple costs 30 yen
> and I have 5 of them, I was taught to multiply 30x5 to arrive at
> 150, not 5x30=150, and I am guessing that is because the former
> matches the natural order of these two numbers (cost, quantity) in
> the language I was taught.
You might be right. I was trying to figure out what is "natural" for me
in these cases, but after thinking about it for 2 minutes, I'm pretty
sure anything resembling "natural" is lost as I try to out-think myself. :)
-Peff
next prev parent reply other threads:[~2016-08-01 21:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 18:18 [PATCH] pass constants as first argument to st_mult() René Scharfe
2016-08-01 16:47 ` Jeff King
2016-08-01 21:00 ` Junio C Hamano
2016-08-01 21:11 ` Jeff King [this message]
2016-08-01 22:31 ` Junio C Hamano
2016-08-03 19:13 ` Jeff King
2016-08-03 19:41 ` Junio C Hamano
2016-08-03 19:49 ` Jeff King
2016-08-03 19:58 ` Junio C Hamano
2016-08-03 19:59 ` Stefan Beller
2016-08-03 20:04 ` Jeff King
2016-08-03 19:56 ` Christian Couder
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=20160801211131.6ernsu74ohod2cin@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
/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 NNTP newsgroup(s).