<span></span>On Friday, December 7, 2012, Thomas Schilling wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 7 December 2012 09:25, Erik Hesselink <<a href="javascript:;" onclick="_e(event, 'cvml', 'hesselink@gmail.com')">hesselink@gmail.com</a>> wrote:<br>
> There is no need to define whenJust, since it is just a specialization<br>
> of forM_ from Data.Foldable.<br>
<br>
I don't know if that's such a good argument. I prefer my code<br>
readable -- too much abstraction can have a seriously bad effect on<br>
that. As a simple rule, if the user has to do type inference in their<br>
head, readability suffers.<br>
<br>
In this case, "forM_" implies we're iterating over something container<br>
like, "whenJust" means "I want to do something if this thing yielded a<br>
result". It depends on the context whether a "Maybe" is behaving more<br>
container-like or is indicating the presence of a result where there<br>
may not have been one.<br>
</blockquote><div><br></div><div>I don't have this problem, but I guess that's just personal. But in general I'm not in favor of adding specialized versions of generalized functions.</div><div><br></div><div>
Erik </div>