unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 50499@debbugs.gnu.org
Subject: bug#50499: 28.0.50; project.el: Root of current project
Date: Fri, 10 Sep 2021 18:08:52 +0200	[thread overview]
Message-ID: <87lf44e7l7.fsf@gmail.com> (raw)
In-Reply-To: <bc37f534-1b99-d80c-de4d-490eae73230a@yandex.ru> (Dmitry Gutov's message of "Fri, 10 Sep 2021 15:16:56 +0300")

On Fri, 10 Sep 2021 at 15:16, Dmitry Gutov <dgutov@yandex.ru> wrote:

> On 10.09.2021 08:26, Augusto Stoffel wrote:
>> I guess most uses of `project-root' will be of the form
>>      (when-let ((p (project-current)))
>>         (project-root p))
>> Or at least this is true in the case of an user who is quickly
>> defining
>> a shortcut command in their config.
>> Wouldn't it make sense to make the PROJECT argument of
>> `project-root'
>> optional, giving the above result when omitted?
>
> Given the way it this works, it would need to be a helper function.

Okay, introducing a new name is probably not worth the trouble for such
a small benefit.  Only if it was possible/easy to overload the existing
function (and make it analogous the typical “&optional BUFFER” kind of
argument) would there be a gain in it, I think.

>
> IIUC cl-defmethod does not support default values for arguments, and
> if it did, we'd have to have an implementation of project-root, etc,
> for nil argument. Which is a bad idea because someone else might not
> want to simply do nothing when there is no project found, and our type
> system would then fail to help them notice that.
>
> I don't mind adding said helper (naming suggestions welcome), but the
> way things work now seems fine to me already. Either you have:
>
>   (project-root (project-current t))
>
> where there is no risk of returning nil, and thus no need for when-let,
> or you call (project-current) first, check it for nil, and then
> _probably_ use some other fallbacks. If you don't have fallbacks, then
> the other approach seems better, no?





  reply	other threads:[~2021-09-10 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10  5:26 bug#50499: 28.0.50; project.el: Root of current project Augusto Stoffel
2021-09-10 12:16 ` Dmitry Gutov
2021-09-10 16:08   ` Augusto Stoffel [this message]
2022-08-25 14:43     ` Lars Ingebrigtsen

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=87lf44e7l7.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=50499@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /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).