<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 4, 2013 at 9:07 AM, Matthew Flatt <span dir="ltr"><<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">At Fri, 3 May 2013 17:29:52 -0400, Eli Barzilay wrote:<br> > A few minutes ago, Robby Findler wrote:<br> > ><br> > > FWIW, this was the bug in redex that prompted me to send this<br> > > message (it was there for some time since it wasn't a syntax error<br> > > .... it was similar in spirit to the code I posted; things broke<br> > > when #f was an argument)<br> ><br> > [I think that it's good to have a much more relaxed policy about<br> > breaking compatibility in cases like this: so far there was no real<br> > code found that uses the feature, but there is one instance of code<br> > that would get fixed by the change...]<br> <br> </div>Well, Ian provided an example from real code, right? Ian is willing to<br> change his code, but the code sounds real.<br> <br> There's also the use in `unparse-pattern' in Redex. Maybe that's the<br> troublesome one that Robby has in mind changing (or he would be happy<br> to change it, obviously), but it's another real example.<br> <br></blockquote><div><br></div><div style>No, that was not the example. The code I sent at the beginning of the thread was an adjusted version of the bug that hid in Redex for, roughly, months. It was a real bug and caused real problems and we knew something was wrong but didn't find it for some time.</div> <div style><br></div><div style>In other words, this isn't some made-up, code cleanliness-based request.</div><div> </div><div style>Robby</div><div style><br></div></div></div></div>