Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unwilling to normalize definitions #726

Open
ice1000 opened this issue Nov 24, 2022 · 6 comments
Open

Unwilling to normalize definitions #726

ice1000 opened this issue Nov 24, 2022 · 6 comments
Labels
feature

Comments

@ice1000
Copy link
Member

ice1000 commented Nov 24, 2022

image
@ice1000
Copy link
Member Author

ice1000 commented Nov 24, 2022

Here, I would like to mark the = function as an 'unwilling to normalize' definition, and hence in the error messages, the 'normalized' terms will not be normalizing them.

(But still unhelpful for these defs, I have to admit)

@ice1000
Copy link
Member Author

ice1000 commented Nov 24, 2022

I think it depends on #51

@imkiva
Copy link
Member

imkiva commented Nov 24, 2022

Did you mean def opaque?

@ice1000
Copy link
Member Author

ice1000 commented Nov 24, 2022

Did you mean def opaque?

That's absolutely not normalizing definitions. It never work! I am thinking about making opaque definitions less opaque in the conversion checker though...

@ice1000
Copy link
Member Author

ice1000 commented Nov 24, 2022

If it works then we won't need this anymore.

@ice1000
Copy link
Member Author

ice1000 commented May 31, 2024

The original problem is no longer a problem for us, but still this feature might be useful

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@imkiva @ice1000