Log message:
lang/guile30: Add link to guix bug report about 3.0.10

Log message:
lang/guile30: Update to 3.0.10

This is a maintenance release of 3.0.

Changes in 3.0.10 (since 3.0.9)

* Notable changes

** Beginnings of support for alternate back-ends

A number of adaptations and additions of as-yet unstable interfaces have
been made to allow third-party projects such as the Hoot
Guile-to-WebAssembly whole-program compiler
(https://spritely.institute/hoot/) to use the Guile front-end and
optimizer.  Depending on how Hoot development goes, we may consider
adding first-class support for WebAssembly as a compilation target;
discussion is welcome on the guile-devel mailing list.

** `define` in all bodies

`define` adds a definition to the body in which it appears, as if each
non-tail definition or expression in that body were a binding in a
surrounding `letrec*` clause.  However, in some places, using `define`
would result in the annoying error "definition in expression context,
where definitions are not allowed", which could be fixed by explicitly
adding a surrounding binding contour, for example an empty `let`.  This
was because there was no implicit surrounding lexical binding contour
for the body of `when` and `unless`, for `cond` clauses, `case` clauses,
`and-let*` bodies, and `with-fluids`.  But no more; now these contexts
now create a binding contour, allowing the use of `define`.

** Two bug fixes of note regarding scoping of top-level variables

Previously, a reference to a top-level variable in a module other than
the current module would be silently rewritten to reference the current
module, if the variable was unbound in its original module.  This was a
hack from the early days of when we extended psyntax to know about the
module system, and is now fixed to properly use the scope of the
introduced binding instead of the scope of the macro use site.

Also, embarrassingly, sometimes macro-introduced top-level variables
would use the same generated name.  This is because of the strategy
discussed in the manual, "Hygiene and the Top-Level"; sometimes the
hashes would collide, for example if two definitions were the same in
the beginning and only differed long into the end.  This has been fixed
to ensure name uniqueness.

* New interfaces and functionality

** R6RS custom textual ports

Guile finally supports this venerable R6RS interface; see "Custom Ports"
in the manual for more.  These ports are suspendable (see "Non-Blocking
I/O").  Also new in this release, custom binary ports are now
suspendable as well.

** New "soft port" interface

Instead of using R6RS custom textual ports, we recommend the new "soft
ports" facility, because it is easier to use while also being more
expressive.  See "Soft Ports" in the manual for more details.

Soft ports are implemented by the new module `(ice-9 soft-ports)`.
There is a legacy "soft ports" facility exported by `(guile)` which will
be deprecated at some point.

** New "custom port" facility: (ice-9 custom-ports)

Custom ports are like R6RS custom binary ports, but lower-level, having
access to all of Guile's internal port API.  See "Custom Ports" in the
manual.

** New surface syntax: Wisp (SRFI-119)

Guile now includes SRFI-119, commonly referred to as Wisp (for
"Whitespace for Lisp"), a Pythonesque surface syntax for Scheme where
parentheses are replaced by equivalent indentation.  See SRFI-119 in the
manual.

** New warning: unused-module

This analysis, enabled at `-W2', issues warnings for modules that appear
in a `use-modules' form or as a #:use-module clause of `define-module',
and whose bindings are unused.  This is useful to trim the list of
imports of a module.

In some cases, the compiler cannot conclude whether a module is
definitely unused---this is notably the case for modules that are only
used at macro-expansion time, such as (srfi srfi-26).  In those cases,
the compiler reports it as "possibly unused".

** New documentation on inline procedure property declarations

Did you know that you can annotate procedures with properties?  It goes
like this:

  (define (frobnicate)
    #((fruits . (apple banana)))
    (whatever))
  (procedure-property frobnicate 'fruits) => (apple banana)

Now you know, and now it is documented in "Procedure Properties" in the
manual.  It has been this way since at Guile 2.0, but was never
documented before.

** New procedure annotation: maybe-unused

The utility of the `-Wunused-toplevel` warning, enabled at `-W2`, has
historically been somewhat limited, especially when a macro generates a
number of bindings, not all of which may be used.  To produce more
useful results, we now allow procedures to set the `maybe-unused`
property, which if true will not result in unused-toplevel warnings.
This property is set by `define-inlinable`, in case an inline binding
never needs the procedure-as-value definition.

** New exports from `(system foreign)`: read-c-struct, write-c-struct

See "Foreign Structs" in the manual.  These macros are like the older
`parse-c-struct` / `make-c-struct` procedures, but they are more
efficient because they inline the field accesses and don't deal in
lists.

** Wider backtraces when not writing to a terminal

When writing a backtrace, if the output port is not a terminal, Guile
truncates the lines at 500 characters instead of 80.  Override this
width via the `default-frame-width` parameter exported by the `(system
repl debug)` module.

** copy-file now supports copy-on-write

The copy-file procedure now takes an additional keyword argument,
#:copy-on-write, specifying whether copy-on-write should be done, if the
underlying file-system supports it.  Possible values are 'always, 'auto
and 'never, with 'auto being the default.

This speeds up copying large files a lot while saving the disk space.

** 'seek' can now navigate holes in sparse files

On systems that support it, such as GNU/Linux, the new SEEK_DATA and
SEEK_HOLE values can now be passed to the 'seek' procedure to change
file offset to the next piece of data or to the next hole in sparse
files.  See "Random Access" in the manual for details.

** ((scm foreign-object) make-foreign-object-type) now supports #:super

A list of superclasses can now be provided via #:super.

** 'get-bytevector-all' is now written in Scheme and is thus suspendable

The 'get-bytevector-all' procedure from (rnrs io ports) and (ice-9
binary-port) used to be implemented in C, making it non-suspendable--a
bummer for programs using suspendable ports and Fibers.  It has been
rewritten in Scheme, addressing this limitation.

* Performance improvements

** Better compilation of calls to procedures with keyword arguments

Calls to keyword-arg functions can now be inlined.  Even when not
inlined, sometimes now we can compute default values for missing
keywords at the callee instead of in the caller.

** Better compilation of append with more than 2 arguments
** Better compilation logand with one immediate argument
** Better type inference for result of symbol-hash
** Elide effect-free primitive calls when called for effect
** Constant folding for string->utf8
** JIT improvements for rarely-used push/pop/drop
** Better type inference for numeric tower predicates
** Better compilation for calls to raise-exception
** Smaller disk usage via sparse binary files

* New deprecations

** (ice-9 lineio)

Use read-line together with unread-string instead.

* Changes to the distribution

** Parallel test driver for Guile unit tests

Guile's internal unit test harness is now compatible with Automake's
parallel test driver, allowing `make check -j20` to use 20 cores, if you
have them.  Send any bug reports to bug-guile@gnu.org.

Log message:
guile30: compilation fix for previous

(posix.c:1573:7: error: label at end of compound statement)

Log message:
guile30: Wrap dprintf() in HAVE_DPRINTF.

Log message:
Use MASTER_SITE_GNU

Log message:
guile30: remove paxctl workaround for JIT on NetBSD

Just disable JIT and wait for a proper upstream fix.
Bug report filed at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61957

Test status on NetBSD has not changed.

Bump PKGREVISION.

Log message:
lang/guile30: Update to 3.0.9

Changes in 3.0.9 (since 3.0.8)

* Notable changes [headlines only; see NEWS]

* New interfaces and functionality

** New `spawn' procedure to spawn child processes

** `open-file' now supports an "e" flag for O_CLOEXEC

** `pipe' now takes flags as an optional argument

** Bindings to `openat' and friends

** Abstract Unix-domain sockets are supported

** New socket-related constants defined

** New `bytevector-slice' procedure

** Disassembler now shows intrinsic names

** Linker and assembler consume less memory

Log message:
guile30: Disable lto

There are unclear issues with lto.  Until that's sorted, just disable
it.  Resolves build failure on NetBSD/i386.

Log message:
*: bump PKGREVISION for libunistring shlib major bump

Log message:
guile30: update to 3.0.8.

Changes in 3.0.8 (since 3.0.7)

* Notable changes

** Cross-module inlining

Although historically Guile has treated modules as glorified hash
tables, most modules are actually _declarative_ -- they just define
functions and variables and provide them for other modules to use, and
don't manipulate modules as first-class objects.  See "Declarative
Modules" in the manual, for more discussion.

Since version 3.0.0, Guile has taken advantage of declarative semantics
to allow a top-level definition to be inlined within its uses in the
same compilation unit, provided the binding is never assigned and
defined exactly once.  Guile 3.0.8 extends this to allow some
exported declarative definitions to be inlined into other modules.

This facility is mostly transparent to the user and is enabled at the
default -O2 optimization level.  "Small" definitions are available for
cross-module inlining (-Oinlinable-exports, included at -O2).  The
actual inlining decision is performed by Guile's partial evaluation pass
(the -Ocross-module-inlining modifier to -Opeval, included at -O2 also),
subject to effort and size growth counters.

Note however that as with macros, when a definition changes in module A,
a separately compiled module B that uses that definition doesn't
automatically get recompiled.  This is a limitation in Guile that we
would like to fix.

As another limitation, cross-module inlining is only available for
imports from modules which have already been compiled at -O2 (or
otherwise with -Oinlinable-exports).

When determining whether to enable this facility by default, we weighed
the usability problems of stale inlined bindings against the benefit of
allowing module boundaries to no longer be optimization boundaries, we
ended up on the "let's do it!" side of the equation.  However we welcome
feedback from users as to what should be the default behavior, until
such a time as we have a proper notion of when a compiled file is stale
or not.

** Avoid the need for a custom GMP allocator

In Guile 3.0.6, we fixed a longstanding bug in Guile's use of the
library that Guile uses to implement bignums (large integers), GMP
(https://gmplib.org).  See the Guile 3.0.6 release notes.  However this
left us with a suboptimal Guile, in which each large integer had to have
a finalizer to free the memory allocated by GMP.  Finalizers take time
and space, and so they limit allocation rate, causing bignum performance
to drop.  Though you could set an environment variable to go back to the
older, faster behavior, it wasn't the default.

In Guile 3.0.8 we fix this problem comprehensively by avoiding embedding
GMP's mpz_t values in Guile bignums.  Instead we embed the bignum digits
directly, avoiding the need for finalizers or custom allocators.  This
removes the need for the GUILE_INSTALL_GMP_MEMORY_FUNCTIONS environment
variable mentioned in the Guile 3.0.6 release notes.  We also deprecate
the scm_install_gmp_memory_functions variable.

* New interfaces and functionality

** Typed vector copy functions in (srfi srfi-4 gnu)

The functions `u8vector-copy' `s8vector-copy' `u16vector-copy'
`s16vector-copy' `u32vector-copy' `s32vector-copy' `u64vector-copy'
`s64vector-copy' `f32vector-copy' `f64vector-copy' `c32vector-copy'
`c64vector-copy' `u8vector-copy!'  `s8vector-copy!'  `u16vector-copy!'
`s16vector-copy!'  `u32vector-copy!'  `s32vector-copy!'
`u64vector-copy!'  `s64vector-copy!'  `f32vector-copy!'
`f64vector-copy!'  `c32vector-copy!'  `c64vector-copy!' have been
added. See SRFI-4 - Guile extensions" in the manual.

** New function srfi-4-vector-type-size in (srfi srfi-4 gnu)

See SRFI-4 - Guile extensions" in the manual.

** `bytevector-fill!' supports partial fill through optional arguments

This is an extension to the r6rs procedure. See "Manipulating
Bytevectors" in the manual.

** `vector-copy!' and `vector-copy' from (rnrs base) included in core

Compared to the previous versions, these accept range arguments. See
"Accessing and Modifying Vector Contents" in the manual.

** New function bitvector-copy

See "Bit vectors" in the manual.

** (system foreign) supports C99 complex types

The types `complex-float' and `complex-double' stand for C99 `float
_Complex' and `double _Complex` respectively.

* Other new optimizations

** Better optimization of "let" in right-hand-side of "letrec"

** Allow constant-folding for calls to "expt"

Thanks to Maxime Devos.

** Add ,optimize-cps REPL meta-command

This meta-command is like ,optimize, but at a lower level.

** Improve alias analysis in common subexpression elimination

** Avoid argument-count checks for well-typed calls to known procedures

This speeds up calls to lexically bound procedures.

** Avoid return-value-count checks for calls to known-return-arity procedures

This new optimization, enabled at -O2, speeds up returns from calls to
lexically bound procedures.

* Build system changes

** Update Gnulib (bugs.gnu.org/49930)

Update gnulib to 8f4538a53d64054ae2fc8b86c0f87c418c6176e6.

** Compile libguile with -flto if available

By default, if the compiler supports link-time optimization via the
-flto flag, Guile will add it to CFLAGS.  This results in a libguile
that is approximately 15% smaller.  Pass --disable-lto to configure to
inhibit this behavior.

** Trim set of prebuilt .go files shipped in the tarball

Guile includes built Scheme files in its tarball to speed up the build,
for casual builders that are less concerned with reproducibility.
However they took a lot of space and we have now trimmed these down to a
more minimal set.  As always, you can remove them and build entirely
from source via a `make -C prebuilt clean`.

* New deprecations

** Vector functions require vector arguments

Passing arrays that are not vectors (arrays for which `(vector? array)'
returns false) to functions `vector-move-left!', `vector-move-right!',
`vector->list', and `vector-copy' is deprecated. Use `array-copy!',
`array-copy', and `array->list' for such arguments.

** `scm_from_contiguous_typed_array' is deprecated

This function was added during the Guile 2.x series and was not
documented and is no longer used in Guile itself.

** Deprecate the "simple vector" concept, `scm_is_simple_vector'

This concept meant to indicate "vectors which aren't array slices".  Use
scm_is_vector.

** Deprecate internal contiguous array flag

We still reserve space for the flag to preserve ABI but it has no
effect.  As such we also remove the internal SCM_I_ARRAY_CONTIGUOUS,
SCM_SET_ARRAY_CONTIGUOUS_FLAG, SCM_CLR_ARRAY_CONTIGUOUS_FLAG,
SCM_I_ARRAY_CONTP preprocessor interfaces, as they were internal and
there is no longer a sensible way of using them.

** Deprecate symbol properties

Symbols used to have a "function slot" and a "property \ 
slot", inherited
from Emacs Lisp and early Lisps, which one would access with
'symbol-pref', 'symbol-fref', 'symbol-pset!', and 'symbol-fset!'.  These
procedures have been discouraged in favor of object properties; they are
now deprecated.  This saves a few words of memory per symbol.

* Bug fixes

** Fix compilation of (ash x N), where N is a literal, at -O1 and below
** Texinfo and XML parsers are now thread-safe (bugs.gnu.org/51264)
** Fix `filename-completion-function' in (ice-9 readline)
** Fix trace-calls-to-procedure (bugs.gnu.org/43102, bugs.gnu.org/48412)
** Fix bug in nftw function (bugs.gnu.org/44182)
** Fix optimization bug in CSE in eq-constant? if both branches same
** Fix readline initialization with invalid keymaps
** Fix crash when reading #nil (bugs.gnu.org/49305)
** Fix read error when reading #{}}#.
** Fix Darwin host detection in foreign-library facility.
** Fix unification of (x ...) patterns in `match'
** Fix scaling floats with leading zeroes in `format'
** Improve support for r7rs-style `(srfi N)' and r6rs-style `(srfi :N)
   module names (bugs.gnu.org/39601, bugs.gnu.org/40371)
** Add support for the ARC architecture (bugs.gnu.org/48816)
** Build fix for const strerror result (bugs.gnu.org/43987)
** Fix typos in SRFI documentation (bugs.gnu.org/50127)
** Fix bounds check in `recvfrom!' (bugs.gnu.org/45595)
** Add support for riscv32
** Limit `ash' to left-shift by 2^32 bits (bugs.gnu.org/48150)
** Fix type confusion in heap-numbers-equal? calls from VM