Re: [racket-dev] struct: exports from 2htdp/image, mrlib/image-core, etc.

When you inject new names, things might break. On Aug 6, 2013, at 9:04 PM, Sam Tobin-Hochstadt wrote: > 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

Re: [racket-dev] "Too many" struct definitions leads to literal error

Thanks --- I've pushed a repair, finally. Unless I'm confused, the problem was a bug in the bytecode format that has been around since v300 or so. At Mon, 5 Aug 2013 15:20:17 -0400 (EDT), "J. Ian Johnson" wrote: > Pushed current branch to > https://github.com/dvanhorn/oaam/tree/thocon > > kcfa.r

Re: [racket-dev] "Too many" struct definitions leads to literal error

Many thanks. First call-with-values/begin0 and now this. I should be the dep bug finder, heh. -Ian - Original Message - From: Matthew Flatt To: J. Ian Johnson Cc: dev Sent: Wed, 7 Aug 2013 11:43:12 -0400 (EDT) Subject: Re: [racket-dev] "Too many" struct definitions leads to literal

[racket-dev] continuation-mark-set->context : Empty Stack Traces?

I'm profiling one of the contract benchmarks[1], and I noticed that sometimes (about 10 out of 300 samples), `continuation-mark-set->context' would return an empty stack trace. This number is cut down by about half if I disable the JIT. These samples seem to be spread out throughout execution (i.e