From: Daniel Colascione <dancol@dancol.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: emacs-devel@gnu.org
Subject: Re: A prototype for a binding based approach to proper namespaces
Date: Sat, 09 May 2020 10:17:48 -0700 [thread overview]
Message-ID: <E1jXT6j-000134-5d@dancol.org> (raw)
In-Reply-To: <xjf7dxlkp1t.fsf@sdf.org>
On May 9, 2020 10:15:29 AM Andrea Corallo <akrl@sdf.org> wrote:
> Daniel Colascione <dancol@dancol.org> writes:
>
>> On May 9, 2020 9:39:18 AM Andrea Corallo <akrl@sdf.org> wrote:
>>
>>> Daniel Colascione <dancol@dancol.org> writes:
>>>
>>>>> I agree with you in principle, but the fact that a pointer chase more is
>>>>> negative for performance in a measurable way or not for this case should
>>>>> be verified with a measure
>>>>
>>>> Death by a thousand cuts is something that happens to lots of real
>>>> world programs. I don't want to introduce unnecessary memory
>>>> indirections or branches where simple and efficient alternatives are
>>>> known to exist and where they're just as good as the inefficient
>>>> option.
>>>
>>> Exactly because we are talking of real world programs I think it should
>>> be measured :)
>>>
>>> I'll maybe have a run using the prototype (so it will prove some
>>> usefulness) and report.
>>
>> No, not in this case. This is something that might appear to be fine
>> in isolated tests or in modules that don't get a lot of use, but the
>> more people use this thing, the worse it gets, right? I don't see any
>> reason to *prefer* this approach to the zero cost one. Let's not be
>> slow for no benefit.
>
> If the alternative is the read time approach I think many people think
> it has disadvantages. Are proposing a third way?
Which specific disadvantages?
> --
> akrl@sdf.org
next prev parent reply other threads:[~2020-05-09 17:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 20:47 A prototype for a binding based approach to proper namespaces Andrea Corallo
2020-05-08 23:43 ` Daniel Colascione
2020-05-09 8:05 ` Andrea Corallo
2020-05-09 15:16 ` Daniel Colascione
2020-05-09 15:50 ` Andrea Corallo
2020-05-09 15:56 ` Daniel Colascione
2020-05-09 16:39 ` Andrea Corallo
2020-05-09 16:41 ` Daniel Colascione
2020-05-09 17:15 ` Andrea Corallo
2020-05-09 17:17 ` Daniel Colascione [this message]
2020-05-09 23:14 ` Andrea Corallo
2020-05-09 23:46 ` João Távora
2020-05-09 23:29 ` Vladimir Sedach
2020-05-09 23:53 ` João Távora
2020-05-10 0:12 ` Daniel Colascione
2020-05-10 4:18 ` Vladimir Sedach
2020-05-10 15:24 ` Andrea Corallo
2020-05-10 17:46 ` Vladimir Sedach
2020-05-10 20:14 ` Andrea Corallo
2020-05-09 7:38 ` Helmut Eller
2020-05-09 8:27 ` Andrea Corallo
2020-05-09 8:50 ` Helmut Eller
2020-05-09 10:57 ` Andrea Corallo
2020-05-09 16:09 ` Dmitry Gutov
2020-05-09 18:08 ` Helmut Eller
2020-05-09 18:55 ` Dmitry Gutov
2020-05-09 22:52 ` Vladimir Sedach
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=E1jXT6j-000134-5d@dancol.org \
--to=dancol@dancol.org \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.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://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).