Does the .guix-authorizations file has some formal grammar, or is it basically "whatever guile does"?

#guix

How do you all prefer your syntax-rules?

(define-syntax-rule (my-when cond body body* ...)
(when cond body body* ...))

for precision or

(define-syntax-rule (my-when cond body ...)
(when cond body ...))

for readability? And what about documentation?

Evaluate @nprofile1q...{body body* ...} ...

or

Evaluate @nprofile1q...{body ...} ...

For me, just `body ...' reads better (both in code and in the manual, but `body body* ...' is more accurate, so I am on the fence about this.

#guile #scheme

match-record does not work with SRFI-9 records, nor with a renamed rtd:

(define <x>* <x>)
(match-record (x) <x>* (f) f)

guix/ui.scm:920:18: Syntax error:
unknown location: match-record: undefined record type in form <x>*

:(

#guix

When loading modules, is the loading serialized or parallel? Especially when threads are involved?

I really hope it is the former, otherwise I am out of ideas how to work around the bugs in our (rnrs records syntactic).

Would anyone here know?

#guile

@nprofile1q... Is there a way to get notified about pushes to some repository, pulling is fine. The best I can currently think of is git ls-remote in a loop, but that is wasteful on both ends, so if there is a better way to get the information I need, it would be great.

Bike shedding time!

I am porting let-alist to #guile . Since there will be some differences, I thought I would name it let-alist*. So far so good.

However, I will also change it to use let*, and I am unsure if that should affect the name.

There are 3 options:

let-alist*
let*-alist
let*-alist*

The last is probably most precise, but it has a little too much * for my taste. I probably like the first the most, despite it being slightly misleading.

Now, what does the internet think?

#scheme

In case you want an #atom feed for a specific issue or pull request for #guix or #guile you can give https://atom.guix.wolfsden.cz a try.

#codeberg (well, #forgejo) only support an Atom/RSS feed for the whole repository, which is not very useful for active repositories.

The performance is not stellar, but *seems* to work fine.

scheme@(guile-user)> 1234
$1 = 1234
scheme@(guile-user)> 12_34
$2 = 1234
scheme@(guile-user)> 123_456_789
$3 = 123456789

Hm, I wonder whether this would be accepted into #guile . Any opinions?