On Thu, Jun 9, 2016 at 2:24 PM, Alex Knauth wrote:
>
>
> There's `define-module-boundary-contract`, which does something similar to
> `define/contract` except that it uses the module as a boundary instead of
> creating it's own:
>
>
> On Jun 9, 2016, at 1:48 PM, Jon Zeppieri wrote:
>
> I think I've asked a question like this in the past, but I still haven't
> found a good solution. I'm going to give a concrete example:
>
> Let's say I have a `date` struct like this:
>
> (struct date (y m d))
>
>
>
I think I've asked a question like this in the past, but I still haven't
found a good solution. I'm going to give a concrete example:
Let's say I have a `date` struct like this:
(struct date (y m d))
And I'm perfectly happy with the default match expander:
(match d
[(date y m d) ...])
But
Hey, I’m the maintainer of the R7RS library. I’d appreciate it if
you filed those issues as bugs on the GitHub repository here:
https://github.com/lexi-lambda/racket-r7rs
I’m glad you found value in the library, and I’d love to try and
fix some of the problems you mentioned, especially since a
Dear Racket developers and users,
I've just tried the non-official implementation of R7RS in Racket.
Three points:
- if you define a library, you can write something like:
(define-library (something)
(export ...) (import ...)
(define another-thing ...)
(define year-another
On 6/8/2016 10:26 PM, David Christiansen wrote:
What I mean is that I'm using draw-pict to cause the contents of a pict
to be drawn on a dc<%> that I get from a bitmap%. The bitmap is
initialized empty and transparent, and then the pict is drawn to it. I
can tell which pixels are affected by
6 matches
Mail list logo