Sorry, instead of clicking the formatting button, I accidentally clicked "send"
prematurely. Continuing below.
On 24.11.24 23:44, Zelphir Kaltstahl wrote:
Hello Guile developers!
Today I ran into a problem simply trying to run `guile`.
I have installed Guile in a guix profile:
$ guix d
Hello Guile developers!
Today I ran into a problem simply trying to run `guile`.
I have installed Guile in a guix profile:
$ guix describe --format=channels
(list (channel
(name 'guix)
(url"https://git.savannah.gnu.org/git/guix.git";)
(branch "master")
(comm
Hi Mikael,
> Guile maintainers might want to consider if we should time this kind
> of change in the API with a particular release. For my part, I think
> we could just add it.
1+
imo as well, there is no need to wait for a particular release [*]
David
[*] especially since you said in another e
Ah... I forgot to complete parse-keyword-formals, which is currently only
rudimentary and doesn't compose the correct argument list for (next-method).
There will be a version 3...
On Sun, Nov 24, 2024 at 3:43 PM Mikael Djurfeldt
wrote:
> Guile maintainers might want to consider if we should tim
Guile maintainers might want to consider if we should time this kind of
change in the API with a particular release. For my part, I think we could
just add it.
On Sun, Nov 24, 2024 at 3:40 PM Mikael Djurfeldt
wrote:
> This is my second attempt at introducing keyword aware methods in GOOPS.
>
> I
This is my second attempt at introducing keyword aware methods in GOOPS.
I was split but finally decided to go with keeping keyword non-aware
define-method and method and introducing keyword aware new syntax method*
and define-method*. Arguments are:
1. It preserves simplicity in method and defin
(It's (define-method (f #:key foo) ...).)
This is a valid point. Certainly there should be unambiguous rules so that
we know which method should be selected. (I planned to examine this aspect
before applying my patch to Guile. I was just eager to share what I had
done in order to collect opinions
