[m-rev.] for post-commit review: go through the queue ops

[Mark Brown]

On Fri, Mar 24, 2023 at 10:38 PM Mark Brown <mark at mercurylang.org> wrote:
>
> On Fri, Mar 24, 2023 at 4:51 AM Zoltan Somogyi
> <zoltan.somogyi at runbox.com> wrote:
> >
> > For review by Mark.
>
> Thanks, that's great.
>
> >
> > There are a couple of issues that this brings up that affect
> > the rest of the document.
> >
> > - Should we use single-character names for variables and
> >   data constructors? I would prefer using meaningful names,
> >   which will be one-character names only in exceptional cases.
> >   For the semantic level, I think one-char names are fine, since
> >   they are common in mathematics texts, but I would prefer
> >   that they were the initial letters of the corresponding variable
> >   names whenever possible, and not x/y/z.
>
> Yes, I think so. I hadn't made a firm decision and figured it would be
> best to wait until there was enough usage to judge, which there is
> now.
>
> Using the math notation that Latex prefers will probably work:
> - function symbols are in normal text with normal spacing
> - variables are single letter and italic
>
> That way variables can be any letter, and still be distinguished from
> constants. Predicate symbols are probably ok written the same as
> function symbols.
>
> I'll try this and see how it works out.

Diffs are attached to address a few XXXs, including notation and
variable names for the queue example. Is it ok to push these, or are
you halfway through something? I'll push this evening if I don't hear
anything.

The notation works ok now, I think. Constructors in the main text are
mostly written in the semantic form which means the font is the same
as the surrounding text, but I think adding the arity makes it
sufficiently clear that a constructor is being referred to.

Mark

>
> >
> > - In the front+back queue representation, I think we should put
> >   the front list before the back list; I think the current order is
> >   counter-intuitive.
>
> Ok, I'll fix that.
>
> Incidentally, I'm doing this outside of work hours now, and will
> assign the new stuff to The Mercury Team. So I'll add a copyright
> message for that at some point.
>
> Cheers,
> Mark
>
> >
> > Zoltan._______________________________________________
> > reviews mailing list
> > reviews at lists.mercurylang.org
> > https://lists.mercurylang.org/listinfo/reviews
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff.small
Type: application/octet-stream
Size: 1159 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20230325/0e9059a4/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff.notation
Type: application/octet-stream
Size: 115065 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20230325/0e9059a4/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff.copyright
Type: application/octet-stream
Size: 719 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20230325/0e9059a4/attachment-0007.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff.small2
Type: application/octet-stream
Size: 2648 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20230325/0e9059a4/attachment-0008.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diff.varnames
Type: application/octet-stream
Size: 18107 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20230325/0e9059a4/attachment-0009.obj>