Got it. Thank you.
On Thu, Jun 24, 2021 at 10:04 AM Matthew Flatt wrote:
> Procedures with contracts are usually implemented by structs that have
> `prop:procedure`. Those applicable structs are not procedures from Chez
> Scheme's perspective. So, in the "Rumble" layer that bridges Chez
> Scheme
Procedures with contracts are usually implemented by structs that have
`prop:procedure`. Those applicable structs are not procedures from Chez
Scheme's perspective. So, in the "Rumble" layer that bridges Chez
Scheme and Racket, care must be taken to use a special `|#%app|` form
instead of direct fu
Great! You're the best, Matt. What was the issue, if it's simple enough to
explain?
On Wed, Jun 23, 2021, 11:53 PM Matthew Flatt wrote:
> Hi David,
>
> Thanks for the report! This is fixed for the next release and in
> the current snapshots.
>
> The repair was commit
>
> cb959879de21406571fb0
Hi David,
Thanks for the report! This is fixed for the next release and in
the current snapshots.
The repair was commit
cb959879de21406571fb0127ded88c54e171c0eb
See also https://github.com/racket/racket/issues/3865
Matthew
At Wed, 23 Jun 2021 22:30:53 -0400, David Storrs wrote:
> I'm seei
The list is fine, but sometimes messages are forgotten because it's
difficult to track them.
If you have a GitHub account, it's better to post is as an issue in
https://github.com/racket/racket
Gustavo
El mié, 23 de jun. de 2021 a la(s) 23:31, David Storrs (
david.sto...@gmail.com) escribió:
>
I'm seeing an "invalid memory reference. Some debugging context lost"
error when using a parameter that has a guard function AND the guard
function is user-defined AND the guard function has a contract on it. What
is the right place to file this aside from the list?
Demonstration:
#lang racket/
6 matches
Mail list logo
