Can you explain what uses would break?
Sam
On Aug 6, 2013 4:21 PM, "Matthias Felleisen" wrote:
>
> That might interfere with normal uses of these libraries in *SL. --
> Matthias
>
>
>
> On Aug 6, 2013, at 6:50 PM, Asumu Takikawa wrote:
>
> > Hi all,
> >
> > A few teaching libraries like `2htdp/
I believe that TR will not look for the struct type descriptor if it
is not in the static struct-info, so removing that might be another
option. Especially since if it isn't provided from the module
regularly.
On Tue, Aug 6, 2013 at 4:21 PM, Matthias Felleisen wrote:
>
> That might interfere with
That might interfere with normal uses of these libraries in *SL. -- Matthias
On Aug 6, 2013, at 6:50 PM, Asumu Takikawa wrote:
> Hi all,
>
> A few teaching libraries like `2htdp/image` provide struct constructors
> and accessors, but don't export the struct type descriptor values. Does
> any
Hi all,
A few teaching libraries like `2htdp/image` provide struct constructors
and accessors, but don't export the struct type descriptor values. Does
anyone mind if I add the exports to libraries like `2htdp/image`,
`mrlib/image-core`, etc.?
(it's needed for Typed Racket with require/typed)
Ch
4 matches
Mail list logo