This patch adds a new special form to explicitly export renamed bindings
from a module:
(export/rename (OLD NEW) ...)
This is mainly useful for supporting R7RS renaming export specifiers (not
done yet).
I wanted first to apply the renamings when creating the module structure,
but it turned
On Mon, Oct 02, 2023 at 06:31:44PM +0200, felix.winkelm...@bevuta.com wrote:
> This patch adds a new special form to explicitly export renamed bindings
> from a module:
>
> (export/rename (OLD NEW) ...)
Why not add it to the regular "export" form? It's already extendable,
as it has syntax:
> On Mon, Oct 02, 2023 at 06:31:44PM +0200, felix.winkelm...@bevuta.com wrote:
> > This patch adds a new special form to explicitly export renamed bindings
> > from a module:
> >
> > (export/rename (OLD NEW) ...)
>
> Why not add it to the regular "export" form? It's already extendable,
> as
Maybe this already works with the current patch, but can we support:
(export (rename foo bar))
As well as the version with the colon (suffix keyword notation) on the end of
export?
Seems like that would be best for symmetry with the import form.
(Sorry, it’s just aesthetics, I know.)
Evan
> Maybe this already works with the current patch, but can we support:
>
> (export (rename foo bar))
>
> As well as the version with the colon (suffix keyword notation) on the end of
> export?
> Seems like that would be best for symmetry with the import form.
>
> (Sorry, it’s just aesthetic
On Tue, Oct 03, 2023 at 12:51:57PM +0200, felix.winkelm...@bevuta.com wrote:
> Ok, I find attached a variant, both more ugly in interface and
> implementation, since ##core#module and functor do not yet allow
> renamings to be handled. Also, "define-interface" has no notion
> of this, so "(rename:
> I'd prefer if we could develop this a bit further to make the rename
> form accessible to module as well.
Sure. I personally never felt the need for rename on export and
wanted to add this just as a base to build R7RS support on.
Bindings and aliases are so easily done in Scheme that it doesn't
On Mon, Oct 09, 2023 at 05:01:47PM +0200, felix.winkelm...@bevuta.com wrote:
> The export/rename localizes the functionality and doesn't
> require changes to existing code. The precedent of the syntax: and
> interface: never was a particularly good one (we should have used separate
> export forms f
On Tue, Oct 10, 2023 at 08:14:54AM +0200, Peter Bex wrote:
> After some more thought on this, I think you convinced me.
> Let's go with the original export/rename patch, unless anyone objects.
A week has passed with no objections. I've pushed the original patch.
Cheers,
Peter
signature.asc
Des