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.

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

Migrate away from overload{}(_, _) in KORE #3988

Closed
4 tasks done
Baltoli opened this issue Feb 14, 2024 · 0 comments
Closed
4 tasks done

Migrate away from overload{}(_, _) in KORE #3988

Baltoli opened this issue Feb 14, 2024 · 0 comments
Assignees

Comments

@Baltoli
Copy link
Contributor

Baltoli commented Feb 14, 2024

Currently, we emit an overload{}(X, Y) attribute on an \equals{X, Y} axiom to encode that Y is a more specific overload of X.

We want to use the overload name for a frontend attribute (#3985), and so will need to change the name of the KORE attribute to support this. Doing so will require a series of changes:

rv-jenkins pushed a commit that referenced this issue Feb 14, 2024
@tothtamas28 tothtamas28 assigned jberthold and Baltoli and unassigned tothtamas28 Feb 15, 2024
rv-jenkins pushed a commit to runtimeverification/haskell-backend that referenced this issue Feb 19, 2024
Part of runtimeverification/k#3988

### Scope:
Renames `overload` attribute to `symbol-overload` (identical
functionality). **No backward compatibility!**

Requires rebase on top of the merged K update #3691

---------

Co-authored-by: Bruce Collie <[email protected]>
@Baltoli Baltoli closed this as completed Feb 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants