[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: example of poor debugging message (follow up Guix Days)
From: |
Felix Lechner |
Subject: |
Re: example of poor debugging message (follow up Guix Days) |
Date: |
Mon, 24 Feb 2025 06:32:14 -0800 |
User-agent: |
mu4e 1.12.8; emacs 29.4 |
Hi,
On Mon, Feb 24 2025, Ricardo Wurmus wrote:
> - it's not always just down to Guile's poor backtraces (which on their own
> can be puzzling, no question about it)
> - on the compilation side of things I think Guix would benefit from
> enforcing type contracts to trigger errors earlier.
Those are deep insights from someone who worked a lot on Guix.
I also wish for validation sometimes but it would be a big departure.
Kind regards
Felix
- Re: example of poor debugging message (follow up Guix Days), (continued)
- Re: example of poor debugging message (follow up Guix Days), Sharlatan Hellseher, 2025/02/21
- Re: example of poor debugging message (follow up Guix Days), Simon Tournier, 2025/02/21
- Re: example of poor debugging message (follow up Guix Days), Ludovic Courtès, 2025/02/23
- Re: example of poor debugging message (follow up Guix Days), Ricardo Wurmus, 2025/02/23
- Re: example of poor debugging message (follow up Guix Days), Sharlatan Hellseher, 2025/02/23
- Re: example of poor debugging message (follow up Guix Days), 45mg, 2025/02/24
- Re: example of poor debugging message (follow up Guix Days), Ekaitz Zarraga, 2025/02/24
- Re: example of poor debugging message (follow up Guix Days), Ricardo Wurmus, 2025/02/24
- Re: example of poor debugging message (follow up Guix Days),
Felix Lechner <=
- Re: example of poor debugging message (follow up Guix Days), 45mg, 2025/02/24
- Re: example of poor debugging message (follow up Guix Days), Andreas Enge, 2025/02/24
Message not available