[m-rev.] for review: define <<u and >>u

Zoltan Somogyi zoltan.somogyi at runbox.com
Tue Dec 6 01:11:07 AEDT 2022


This diff is boring, since it makes each change ten times
(one set of changes to library/{int,uint}*.m, and another set
to tests/hard_coded/bitwise_{int,uint}*.m), but once you have
checked one copy, you can just check whether it was copied
correctly to the other nine files.

Since this diff requires the installed compiler to recognize <<u and >>u
as operators, I won't commit this until an rotd contains the both
the change that enables that, and the new synonym for
compiler-sufficiently-recent that I just added to options.m in order to allow
configure to test for that. This won't be before wednesday. I will
post the proposed update to NEWS before then.

Zoltan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Log.ushift
Type: application/octet-stream
Size: 1415 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20221206/33a936ce/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.ushift
Type: application/octet-stream
Size: 71801 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20221206/33a936ce/attachment-0003.obj>


More information about the reviews mailing list