Re: [PATCH] Fix potential invalid argument error in `##sys#decompose-import'

2020-05-03 Thread Evan Hanson
On 2020-05-03 11:44, felix.winkelm...@bevuta.com wrote: > I'd love to apply your patches, but can you remove the "noprefix=true" option > from your .git/config, please? Apparently git am doesn't recognize this patch. Yes, apologies, I'll fix it for future patches. I didn't consider that Git might

Re: Fwd: Comments on draft #3

2020-05-03 Thread John Cowan
The behavior of a macro keyword in operand position is not affected by the patch. On Sun, May 3, 2020 at 1:04 PM Peter Bex wrote: > On Sun, May 03, 2020 at 12:55:40PM -0400, John Cowan wrote: > > This is the first of two patches that allow macros to be expanded when > they > > appear in operand

Re: Fwd: Comments on draft #3

2020-05-03 Thread Peter Bex
On Sun, May 03, 2020 at 12:55:40PM -0400, John Cowan wrote: > This is the first of two patches that allow macros to be expanded when they > appear in operand position, so that if pi is a macro for 3.14159, then (+ 5 > pi) will be expanded to (+ 5 3.14159). This allows macros that work like > proce

Fwd: Comments on draft #3

2020-05-03 Thread John Cowan
This is the second of two patches that allow macros to be expanded when they appear in operand position. It allows a syntax-rules pattern to be a single variable rather than a list; this rule will be used when the macro keyword is in operand position. -- Forwarded message - From:

Fwd: Comments on draft #3

2020-05-03 Thread John Cowan
This is the first of two patches that allow macros to be expanded when they appear in operand position, so that if pi is a macro for 3.14159, then (+ 5 pi) will be expanded to (+ 5 3.14159). This allows macros that work like procedures in the sense that they can be passed as operands. This patch

Re: [PATCH] force finalizers only if finalizers exist

2020-05-03 Thread megane
felix.winkelm...@bevuta.com writes: >> On 2020-04-07 14:51, felix.winkelm...@bevuta.com wrote: >> > > > This patch disables the final GC for finalizer forcing at normal >> > > > program termination >> > > > if no finalizers are live as the GC is unnecessary in such cases. >> > > >> > > How abou

Re: More millisecond procedures

2020-05-03 Thread Peter Bex
On Sun, May 03, 2020 at 03:48:46PM +0300, Lassi Kortela wrote: > > Attached is a set of two patches. The first one simply adds a > > deprecation notice to current-milliseconds and adds the new procedure > > current-process-milliseconds. > > Racket also has `current-inexact-milliseconds`: "Returns

More millisecond procedures

2020-05-03 Thread Lassi Kortela
Attached is a set of two patches. The first one simply adds a deprecation notice to current-milliseconds and adds the new procedure current-process-milliseconds. Racket also has `current-inexact-milliseconds`: "Returns the current time in milliseconds since midnight UTC, January 1, 1970. The r

[PATCH] Deprecate current-milliseconds in favor of current-process-milliseconds and improve behaviour a bit [was: Re: Exposing subsecond precision in current-seconds]

2020-05-03 Thread Peter Bex
On Thu, Apr 30, 2020 at 12:11:31PM +0200, felix.winkelm...@bevuta.com wrote: > > Yeah, like I said in my other message, we could use the name > > current-process-milliseconds, like Racket; > > https://docs.racket-lang.org/reference/time.html > > > > I like the name, because it's pretty clear what i

Re: [PATCH] Mark identifiers used to collect profiling info as `bound-to-procedure'

2020-05-03 Thread felix . winkelmann
> Calls to `##sys#register-profile-info' and `set-profile-info-vector!` > are inserted into the program when profiling is enabled, so they should > be marked as procedures so the resulting call nodes are marked as safe, > just like we do for the `##sys#profile-entry' and `exit' procedures. Pushed

Re: [PATCH] Fix potential invalid argument error in `##sys#decompose-import'

2020-05-03 Thread felix . winkelmann
> This fixes a small bug in `##sys#decompose-import' where "spec" (which > is a list) is passed to the `warn' procedure rather than "name" (which > is a symbol, as expected). This leads to an invalid argument error > arising from `symbol->string', e.g. > Pushed. felix

Re: [PATCH] Fix potential invalid argument error in `##sys#decompose-import'

2020-05-03 Thread felix . winkelmann
> On Sun, May 03, 2020 at 11:44:00AM +0200, felix.winkelm...@bevuta.com wrote: > > I'd love to apply your patches, but can you remove the "noprefix=true" > > option > > from your .git/config, please? Apparently git am doesn't recognize this > > patch. > > git am -p0 > > should do the trick. It to

Re: [PATCH] Fix potential invalid argument error in `##sys#decompose-import'

2020-05-03 Thread Sebastien Marie
On Sun, May 03, 2020 at 11:44:00AM +0200, felix.winkelm...@bevuta.com wrote: > I'd love to apply your patches, but can you remove the "noprefix=true" option > from your .git/config, please? Apparently git am doesn't recognize this patch. git am -p0 should do the trick. It told to `git apply' that

Re: [PATCH] Fix potential invalid argument error in `##sys#decompose-import'

2020-05-03 Thread felix . winkelmann
I'd love to apply your patches, but can you remove the "noprefix=true" option from your .git/config, please? Apparently git am doesn't recognize this patch. felix