match on strings vs. match on Python ID for compiler builtins #105

New Issue

sb10q · 2021-11-21T11:34:44+08:00

sb10q commented

2021-11-21 11:34:44 +08:00

e.g. #98 (comment)
decide what to do (also taking nac3standalone into account)
review use throughout the codebase

* e.g. https://git.m-labs.hk/M-Labs/nac3/pulls/98#issuecomment-3189 * decide what to do (also taking nac3standalone into account) * review use throughout the codebase

sb10q added the

low-priority

label 2021-11-21 11:34:44 +08:00

sb10q referenced this issue

2021-11-21 11:35:27 +08:00

Constant Default Parameter Support #98

ychenfo commented

2021-12-11 15:50:19 +08:00

One way that I currently think of is that maybe we can later add a function to symbol resolver to resolve these 'special marker symbols' (I am not sure whether this is a good wording for this. But I think we need to add this function in symbol resolver trait because they are not always types in nac3core, just markers...).

Then in nac3artiq we can match by id and in nac3standalone we can just match by string.

One way that I currently think of is that maybe we can later add a function to symbol resolver to resolve these 'special marker symbols' (I am not sure whether this is a good wording for this. But I think we need to add this function in symbol resolver trait because they are not always types in nac3core, just markers...). Then in nac3artiq we can match by id and in nac3standalone we can just match by string.

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/nac3#105