I'm not surprised, I pretty much expected this response, but I'm curious what the difficulty was. Is cond-as-void relied on that much more pervasively than mutable pairs? Is it exceedingly hard to add else-clauses to all the necessary conds? You two, Robby and Matthew, probably have a better idea than I do about the prevailing trends in the Racket code base.<br>
<br clear="all">Carl Eastlund<br><br><div class="gmail_quote">On Tue, Oct 2, 2012 at 10:36 AM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu" target="_blank">robby@eecs.northwestern.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">IIRC, we even experimented with this one briefly and quickly gave up<br>
as we got overwhelmed.<br>
<span class="HOEnZb"><font color="#888888"><br>
Robby<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Tue, Oct 2, 2012 at 9:22 AM, Matthew Flatt <<a href="mailto:mflatt@cs.utah.edu">mflatt@cs.utah.edu</a>> wrote:<br>
> I think this a great change for a future `racket2' (someone should be<br>
> keeping a list of these), but it's too incompatible a change for `cond'<br>
> in `racket'.<br>
><br>
> At Tue, 2 Oct 2012 09:52:38 -0400, Carl Eastlund wrote:<br>
>> I often wish cond would raise an exception if all the tests failed and<br>
>> there were no else clause. I have taken to writing a macro to enforce<br>
>> this; I usually call it cond!. The void default for cond seems like an<br>
>> un-Racketish holdover from primarily-imperative programming. With some of<br>
>> the other changes we've made in Racket, are we willing to consider changing<br>
>> the fall-through behavior of cond? It seems like an experiment worth<br>
>> running to me.<br>
>><br>
>> If not, I would at least like to add an erroring version of cond somewhere<br>
>> in the language. It's a shame to have to keep writing such a primitive<br>
>> feature. Right now in my dracula github repo I have cond! implemented in<br>
>> racket/cond and re-exported from racket, but I'm not thrilled about either<br>
>> the location or the name. I kept it out of racket/base so I could depend<br>
>> on the syntax collection for good source location reporting in the error<br>
>> message.<br>
>><br>
>> Carl Eastlund<br>
>> _________________________<br>
>> Racket Developers list:<br>
>> <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
> _________________________<br>
> Racket Developers list:<br>
> <a href="http://lists.racket-lang.org/dev" target="_blank">http://lists.racket-lang.org/dev</a><br>
<br>
</div></div></blockquote></div><br>