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

K 3988 rename overload attribute #3723

Merged
merged 2 commits into from
Feb 19, 2024
Merged

Conversation

jberthold
Copy link
Member

@jberthold jberthold commented 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

@Baltoli
Copy link
Contributor

Baltoli commented Feb 19, 2024

Thanks @jberthold; looks good to me! Will let you take care of the rebase cleanup + merge once the required changes are all in place.

@jberthold jberthold force-pushed the k-3988-rename-overload-attribute branch from 82a871c to bdced7e Compare February 19, 2024 21:22
@jberthold jberthold marked this pull request as ready for review February 19, 2024 21:22
@rv-jenkins rv-jenkins merged commit ac6908d into master Feb 19, 2024
7 checks passed
@rv-jenkins rv-jenkins deleted the k-3988-rename-overload-attribute branch February 19, 2024 22:02
rv-jenkins pushed a commit to runtimeverification/k that referenced this pull request Feb 20, 2024
The backends have now all been changed to accept the new
`symbol-overload` KORE attribute
(runtimeverification/llvm-backend#984,
runtimeverification/haskell-backend#3723) and so
we can safely stop the frontend from emitting the old `overload` syntax.

Downstream testing on the C semantics (which makes heavy use of
overloading) has passed, so I'm confident this change is correct.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants