[m-rev.] for review: move pred_origins closer to being a structured pred name

Zoltan Somogyi zoltan.somogyi at runbox.com
Sat Jul 23 09:28:31 AEST 2022


2022-07-19 19:45 GMT+10:00 "Zoltan Somogyi" <zoltan.somogyi at runbox.com>:
> 4. I intend to refactor the pred_origin type so it has five function symbols
> 
>    - one for user defined predicates and functions
>    - one for compiler defined predicate and functions that users can possibly
>      explicitly refer to, such as mutable getters and setters
>    - one for compiler defined predicate and functions that users cannot
>      explicitly refer to, such as those implementing lambdas
>    - one for compiler defined predicate and functions that result from
>      the transformation of another *predicate*
>    - one for compiler defined predicate and functions that result from
>      the transformation of another *procedure*
> 
>    The reason for the refactor is that several parts of the compiler care about
>    only one, or a few, of these categories, and listing the other categories in
>    the relevant switches is both simpler and requires less maintenance than
>    listing all the other pred_origins.

The attached diff does a modified version of this. For review by anyone.

Zoltan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Log.po2
Type: application/octet-stream
Size: 958 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20220723/015e6808/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIFF.po2
Type: application/octet-stream
Size: 127019 bytes
Desc: not available
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20220723/015e6808/attachment-0003.obj>


More information about the reviews mailing list