On Sun, Jan 12, 2020, 12:59 PM Andy Wingo wrote:
> On Sat 14 Dec 2019 07:16, Aleix Conchillo Flaqué
> writes:
>
> > BOOTSTRAP GUILEC system/vm/linker.go
> > /bin/sh: line 1: 69110 Abort trap: 6 GUILE_AUTO_COMPILE=0
> ../meta/build-env guild compile --target="x86_64-apple-darwin18.7.0
On Sun 04 Aug 2019 00:46, Caleb Ristvedt writes:
> In Guile 2.2.6 as packaged on Guix System (x86-64), the following
> happens:
>
> --
> (define some-fluid (make-thread-local-fluid 42))
>
> (display (fluid-ref some-fluid))
>
> => #f
> --
Applied to both branches. Thanks for the patch and thanks also to Mark
for the review and initial patch!
In the future, Tim, if you have larger patches, we should work out
copyright assignment paperwork. But less-than-10-line patches are fine
without. Let me know if this is of interest to you.
On Sat 07 Dec 2019 01:12, Kiyoshi KANAZAWA writes:
> Hello,
>
> Trying guile-2.9.6.
> Make fails on Solaris x86/64 with 32 bit mode.
> It does not happen with 64 bit mode.
>
> $ make
> :
> CC libguile_3.0_la-ioext.lo
> CC libguile_3.0_la-jit.lo
> jit.c: In function 'compile_s64_
On Sun 08 Dec 2019 18:41, Rob Browning writes:
> For example, in 2.2.6:
>
> scheme@(guile-user)> (define x (make-thread-local-fluid 'default))
> scheme@(guile-user)> (fluid-ref x)
> $1 = #f
Applied your patch on both branches; thank you!
Andy
On Sat 14 Dec 2019 07:16, Aleix Conchillo Flaqué writes:
> BOOTSTRAP GUILEC system/vm/linker.go
> /bin/sh: line 1: 69110 Abort trap: 6 GUILE_AUTO_COMPILE=0
> ../meta/build-env guild compile --target="x86_64-apple-darwin18.7.0" -O1
> -Oresolve-primitives -L
> "/Users/aleix/guile-2.9.
On Thu 19 Dec 2019 17:24, Marc Nieper-Wißkirchen
writes:
> I've read in the news that the upcoming Guile 3.0 will unify records.
>
> Core records type seem to support the procedure "record-accessor",
> which takes a field name as a symbol.
>
> In R7RS (based on SRFI 9), record field names are, h
On Sat 14 Dec 2019 14:31, Göran Weinholt writes:
> The following program works in Guile 2.2.6 (and other R6RS
> implementations), but raises an exception in Guile 2.9.7. A field called
> "name" exists in record type a and record type b, but there is no actual
> naming conflict as I understand it.
On Sun 15 Dec 2019 02:02, Christopher Lam writes:
> See snippet below.
> IMHO the second call to add1 should fail. On guile-2.2.6 it does not error
> out.
> On guile-2.0 it does throw error (as I think it should).
> Is this intentional?
OMG what an embarrassing bug! Thank you for finding and
On Fri 03 Jan 2020 16:56, Ludovic Courtès writes:
> It seems that since 2.9.7, autoloads have to specify exactly all the
> bindings of the autoloaded module that the user will ever reference.
> Bindings that are omitted from the #:autoload clause remain unbound:
Indeed. This was an unintentiona
Thanks for the report; fixed! Patches welcome if there are any bugs :)
Cheers,
Andy
11 matches
Mail list logo
