[m-dev.] [Mercury-Language/mercury] Segfault in only Mercury after solutions in a particular code path (#72)

[Zoltan Somogyi]

On Tue, 27 Aug 2019 11:32:26 +1000, Peter Wang <novalazy at gmail.com> wrote:
> For me, it's fine to break compatibility across rotds. Few users (zero?)
> would have such big programs that rebuilds are of any concern.

Agreed. The issue I see is that they have to *know* that they should rebuild
from scratch. If they don't, and try to mix .c files generated by Mercury compilers
from before and after the change, the result will be mysterious failures.

> > Note that we should remove the "where direct_arg is" syntax on type definitions
> > sometime, since the compiler can now do at least as good a job as humans
> > at deciding when the optimization is applicable (provided it is switched on, of course).
> > Flip-the-switch time would be as good a time as any for this, which makes *now*
> > a good time for its deprecation.
> 
> Sure.

OK, I will add a note to NEWS, and post to m-users.

Zoltan.