From: Maciej Kalandyk via "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile@gnu.org>
To: 63304@debbugs.gnu.org
Subject: bug#63304: srfi-69 weak table bug
Date: Fri, 05 May 2023 13:39:49 +0200 [thread overview]
Message-ID: <DEO6UR.9NO8S4T6MMTI3@ardigen.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 639 bytes --]
Tested on: Fedora, Guix
Fedora's guile package: guile30-3.0.7-8.fc38.x86_64
Fedora guile --version: 3.0.7
Guix guile package: 1.4.0-5.286cdf0
Guix guile --version: 3.0.9
How to reproduce:
```scheme
(use-modules (srfi srfi-69))
(define tmp (make-hash-table #:weak 'key))
(hash-table-set! tmp 'test 10)
```
Error:
```
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
In procedure scm_hash_fn_create_handle_x: Wrong type argument in
position 1 (expecting hash-table): #<weak-table 0/31>
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
```
Description: using #:weak option causes hash-table-set! to crash
[-- Attachment #2: Type: text/html, Size: 937 bytes --]
reply other threads:[~2023-05-05 11:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DEO6UR.9NO8S4T6MMTI3@ardigen.com \
--to=bug-guile@gnu.org \
--cc=63304@debbugs.gnu.org \
--cc=maciej.kalandyk@ardigen.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.
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).