[m-rev.] for review: announce a bunch of bug fixes

Peter Wang novalazy at gmail.com
Mon Jan 6 17:31:55 AEDT 2020


On Mon, 6 Jan 2020 16:50:46 +1100 (AEDT), Julien Fischer <jfischer at opturion.com> wrote:
> 
> Hi Peter,
> 
> On Mon, 6 Jan 2020, Peter Wang wrote:
> 
> > On Mon, 6 Jan 2020 16:11:14 +1100 (AEDT), Julien Fischer <jfischer at opturion.com> wrote:
> >> -* We have fixed a long-standing bug causing crashes in deep profiling
> >> -  grades, related to unify/compare for tuples. [Mantis bug #3]
> >> -
> >>   * We have fixed some bugs with constrained polymorphic modes.
> >>
> >>   * The compiler now reports an error for binary/octal/hexadecimal integer
> >>     literals that cannot be represented in the compiler's native `int` type.
> >>
> >> +* [Mantis bug #3]. We have fixed a long-standing bug causing crashes in
> >> +  deep profiling grades, related to unify/compare for tuples.
> >> +
> >
> > I prefer the bug number at the end, with no full stop after the closing
> > bracket.
> 
> The problem with that is that its more likely to end up with weird
> looking line breaks in the HTML version (i.e. in the middle of the
> reference to the bug).

Yes, I see. You could prevent the line breaks with no-break spaces,
either writing   or using a pandoc extension (backslash space),
both of which reduce readability of the plain text, or enter U+00A0
directly. Meh.

Peter


More information about the reviews mailing list