unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret <dev@jpoiret.xyz>
To: Ricardo Wurmus <rekado@elephly.net>, zimoun <zimon.toutoune@gmail.com>
Cc: "Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Guix Devel" <guix-devel@gnu.org>,
	"Tobias Geerinckx-Rice" <me@tobias.gr>,
	"Mathieu Othacehe" <othacehe@gnu.org>,
	"Christopher Baines" <mail@cbaines.net>
Subject: Re: Exception: srfi-35 vs (ice-9 exceptions (was Re: [bug#60802] [PATCH v2 1/2] platforms: Raise an exception when no suitable platform is found.)
Date: Tue, 17 Jan 2023 20:58:31 +0100	[thread overview]
Message-ID: <875yd5kk60.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87bkmyje7v.fsf@elephly.net>

Hi everyone,

I also don't see how Guix would gain anything from moving
to Guile's native exceptions.  However, one thing that would be nice to
have is a description of all such "implementation choices" in Guix,
perhaps in the "Coding style" section of the manual.  Having a
definitive reference to what is the current accepted coding style would
probably help newcomers, more than the actual choice of one specifi
implementation over another.

Best,
-- 
Josselin Poiret


  reply	other threads:[~2023-01-17 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230114041903.7121-2-maxim.cournoyer@gmail.com>
     [not found] ` <87o7r19ocn.fsf@gnu.org>
     [not found]   ` <87mt6i5q4q.fsf@gmail.com>
2023-01-16 20:13     ` Exception: srfi-35 vs (ice-9 exceptions (was Re: [bug#60802] [PATCH v2 1/2] platforms: Raise an exception when no suitable platform is found.) zimoun
2023-01-16 21:59       ` Maxim Cournoyer
2023-01-17 16:35         ` Ludovic Courtès
2023-01-16 22:35       ` Ricardo Wurmus
2023-01-17 19:58         ` Josselin Poiret [this message]
2023-01-19 14:38           ` Ludovic Courtès
2023-01-19 15:59             ` Katherine Cox-Buday

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=875yd5kk60.fsf@jpoiret.xyz \
    --to=dev@jpoiret.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    --cc=maxim.cournoyer@gmail.com \
    --cc=me@tobias.gr \
    --cc=othacehe@gnu.org \
    --cc=rekado@elephly.net \
    --cc=zimon.toutoune@gmail.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).