From: Dmitry Gutov <dmitry@gutov.dev>
To: Alan Mackenzie <acm@muc.de>
Cc: "Po Lu" <luangruo@yahoo.com>,
"João Távora" <joaotavora@gmail.com>,
emacs-devel@gnu.org
Subject: Re: master 78fc49407b8 1/3: Improve filling of ChangeLog entries
Date: Wed, 31 Jan 2024 22:39:44 +0200 [thread overview]
Message-ID: <ee6879e4-ea37-4f0d-8b71-3dd95273f6c1@gutov.dev> (raw)
In-Reply-To: <ZbqVUz0uF4TatBmo@ACM>
On 31/01/2024 20:45, Alan Mackenzie wrote:
> Hello, Dmitry.
>
> On Wed, Jan 31, 2024 at 19:05:57 +0200, Dmitry Gutov wrote:
>> On 31/01/2024 17:32, Alan Mackenzie wrote:
>>> On Wed, Jan 31, 2024 at 17:15:41 +0200, Dmitry Gutov wrote:
>>>> On 31/01/2024 16:01, Po Lu wrote:
>>>>> See any file in CC Mode,
>
>>>> No shortage of maintainers, you say?
>
>>> None.
>
>> One cannot name a package with bus factor of 1 and say it has plenty of
>> people willing to maintain it.
>
> What's a "bus factor" in this context?
The smallest number of developers who would need to mysteriously
disappear, for it to become a problem for the project.
> It would appear that one person,
> me, is indeed enough to maintain it. The rate of bugs reported for it
> has sunk to near zero, possibly because of the release of the tree sitter
> C Mode in Emacs 29.1.
That's good.
>> I don't mean to criticize your work (not knowing the exact tradeoffs),
>> but it's plainly a bad example.
>
> Bad example of what?
Of a body of Lisp code maintained by different developers, who all
accepted (and possibly chosen) its current style, thereby justifying it
as something usable as a standard, rather than only a personal preference.
> [ .... ]
>
>>> After several days of struggling with named-let, cl-labels, and friends,
>>> I vote for the plain Lisp, even if it does need more lines to express.
>>> It is simply less work.
>
>> I've never used named-let, and very rarely cl-labels.
>
> I've never used either, but still need to debug them. :-(
edebug usually helps, no?
>> The latter is a very simple idea, though: create a bunch of local
>> function definitions. Like nested functions in Python, for example.
>
> It's a complicated macro. Why is it needed at all? Is there anything
> using it that couldn't be conveniently written in plain Lisp?
Having local variable bindings with lambda values is a little messier in
comparison. For example, the use of cl-labels in
'comp-collect-rev-post-order' seems easy to read and thus justified.
Also, it allows having mutually recursive functions, which won't be an
option in sequential bindings (but I don't see this property taken
advantage of much).
next prev parent reply other threads:[~2024-01-31 20:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170643232559.30479.16631610453249222615@vcs2.savannah.gnu.org>
[not found] ` <20240128085846.187A2C1DAE4@vcs2.savannah.gnu.org>
2024-01-28 13:22 ` master 78fc49407b8 1/3: Improve filling of ChangeLog entries Dmitry Gutov
2024-01-28 13:37 ` Po Lu
2024-01-30 22:07 ` João Távora
2024-01-31 6:43 ` Po Lu
2024-01-31 10:28 ` João Távora
2024-01-31 11:19 ` Po Lu
2024-01-31 13:22 ` João Távora
2024-01-31 14:01 ` Po Lu
2024-01-31 14:30 ` João Távora
2024-01-31 15:15 ` Dmitry Gutov
2024-01-31 15:32 ` Alan Mackenzie
2024-01-31 16:46 ` João Távora
2024-01-31 18:29 ` Alan Mackenzie
2024-01-31 17:05 ` Dmitry Gutov
2024-01-31 18:45 ` Alan Mackenzie
2024-01-31 20:39 ` Dmitry Gutov [this message]
2024-01-29 20:13 ` Stefan Kangas
2024-01-30 1:26 ` Po Lu
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=ee6879e4-ea37-4f0d-8b71-3dd95273f6c1@gutov.dev \
--to=dmitry@gutov.dev \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=luangruo@yahoo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.