Re: Re-exporting a replaced binding

2020-01-06 Thread Ludovic Courtès
Hi! Andy Wingo skribis: > On Fri 03 Jan 2020 19:30, Ludovic Courtès writes: [...] >> Should the #:re-export clause propagate the replace bit, or should >> it not? :-) > > It is a good question :) Before, if you re-exported a #:replace > binding, it wasn't possible to have it be exported wit

Re: Re-exporting a replaced binding

2020-01-05 Thread Andy Wingo
On Fri 03 Jan 2020 19:30, Ludovic Courtès writes: > I’m not sure if this is an intended consequence of > cf08dbdc189f0005cab6f2ec7b23ed9d150ec43d, so I thought I’d share this > example of a practical effect: > > ludo@ribbon /tmp [env]$ cat x.scm > (define-module (x) > #:use-module (srfi srfi-1)

Re: Re-exporting a replaced binding

2020-01-04 Thread Taylan Kammer
On 03.01.2020 19:30, Ludovic Courtès wrote: > > Should the #:re-export clause propagate the replace bit, or should > it not? :-) The 2.9.8 release notes say one should use #:re-export-and-replace for this use-case. Happy new year! Taylan

Re-exporting a replaced binding

2020-01-03 Thread Ludovic Courtès
Hi again! I’m not sure if this is an intended consequence of cf08dbdc189f0005cab6f2ec7b23ed9d150ec43d, so I thought I’d share this example of a practical effect: --8<---cut here---start->8--- ludo@ribbon /tmp [env]$ cat x.scm (define-module (x) #:use-module (