<div dir="ltr"><div><div>Matthew, <br></div>Out of curiosity, could you explain why you'd prefer #:else everywhere instead of [else ...] ?<br></div><div>Would such an #:else allow for multi-line bodies?<br></div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 4, 2013 at 5:06 PM, 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="HOEnZb"><div class="h5">At Sat, 4 May 2013 09:15:22 -0500, Robby Findler wrote:<br>
> On Sat, May 4, 2013 at 9:07 AM, Matthew Flatt <<a href="mailto:mflatt@cs.utah.edu">mflatt@cs.utah.edu</a>> wrote:<br>
><br>
> > 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>
> > 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>
> ><br>
> No, that was not the example. The code I sent at the beginning of the<br>
> thread was an adjusted version of the bug that hid in Redex for, roughly,<br>
> months. It was a real bug and caused real problems and we knew something<br>
> was wrong but didn't find it for some time.<br>
><br>
> In other words, this isn't some made-up, code cleanliness-based request.<br>
<br>
</div></div>Yes, I understand that you faced a real bug. I hedged above on<br>
`unparse-pattern' not to suggest that your actual bug was<br>
uninteresting, but to suggest that I might misunderstand the<br>
relationship between the bug and the current state of our repository.<br>
<br>
All else being equal, I'm definitely in favor of a change to a sensible<br>
`else' for `match'. The "else" that isn't equal, however, is backward<br>
compatibility, and I think we're at the right point in our development<br>
cycle to defer backward incompatibilities to the next language ---<br>
hence my vote to defer.<br>
<div class="HOEnZb"><div class="h5"><br>
_________________________<br>
Racket Developers list:<br>
<a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
</div></div></blockquote></div><br></div>