[Haskell-cafe] A suggestion: On why code merges should influence Haskell design

Sven Panne svenpanne at gmail.com
Wed Oct 14 07:23:39 UTC 2015

2015-10-13 22:08 GMT+02:00 Dimitri DeFigueiredo <defigueiredo at ucdavis.edu>:

> [...] I hadn't looked at how to actually go about writing the "bug-free"
> merge tool (if it becomes possible to write one).

Isn't the whole approach limited by Rices's theorem? (
https://en.wikipedia.org/wiki/Rice%27s_theorem) In general we have to deal
with partial functions, and the property you're talking about is definitely
not trivial in the theorem's sense. So this implies 2 choices:

   * You don't detect all problems caused by merging (no point in putting
some effort into that approach, it's basically what we have today with
plain 'git merge').

   * You have false positives, i.e. the merge tool complains although the
merge is OK.

So the best you can do AFAICT is to keep the amount of false positives low,
hoping that people will see a benefit for the added annoyances.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20151014/58a1b95b/attachment.html>

More information about the Haskell-Cafe mailing list