-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guile deprecation warning due to bit-count #79
Comments
FTR, the current (apparently failed?) attempt at fixing it was discussed in: #66 |
What about replacing guile-3 case of |
unfortunately guile is too smart: x.scm:
|
This code in
gives
And on freshly built 3.0.2:
EDIT: There was a bug in the proposed sol'n above: |
The above might be slower, but only for 3.0, to 3.0.2.
|
FTR, this in a file:
still leads to this:
what we need here is a
i'm just not sure where to add it:
|
or this should also work:
|
@attila-lendvai Or maybe just something like: (define bitvector-count
(or (and=> (module-variable the-scm-module 'bitvector-count) variable-ref)
(lambda (v) (bit-count #t v)))) |
@civodul strangely enough that works indeed! i thought the deprecation warning trap is installed at reading the variable, but your solution would trigger that, too. maybe the trap is ignored at toplevel-form-evaluation/compilation-time? either way, thanks for pointing out a much simpler solution! |
here:
fibers/fibers.scm
Line 38 in 8f4ce08
the issue is that the reference to
bit-count
is not eliminated completely at expand time, it's only guarded by a runtimeif
.not the end of the world, but due to this Shepherd services in Guix print this enormous warning, mutiple times:
The text was updated successfully, but these errors were encountered: