Hi all, On 2015-10-09 15:50:07 -0400, Ryan Culpepper wrote: > If you have any bug-fixes and changes that need to go in the release > then make sure to specify that in the commit message or mail me the > commit SHA1s. You can `git checkout release' to try it out directly if > needed -- but do not try to push commits on it (the server will forbid > it).
I don't have a bug fix for this, but I do think the current problems in the macro debugger (due to the new expander) are worth blocking the release on. Currently if you use the macro debugger on these programs it will error: #lang racket (class object% (super-new)) or #lang typed/racket These problems are tracked as issues 5 and 7 on GH https://github.com/racket/macro-debugger/issues/5 https://github.com/racket/macro-debugger/issues/7 The reason I think these are worth blocking over is that the macro debugger is a widely used tool and it's easy to stumble on these broken cases. Any thoughts? Cheers, Asumu -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/20151020162505.GR17250%40simplyrobot.org. For more options, visit https://groups.google.com/d/optout.
