Skip to content

Conversation

@ssyram
Copy link

@ssyram ssyram commented Sep 19, 2025

This is to work with AeneasVerif/charon#814 . With the vtable_safe (bool) changed to vtable_receiver (Option<Ty>), the VtableMethod is now free from the Ty parameters.

@Nadrieril
Copy link
Member

Btw you may have guessed but you can entirely ignore CI failures in this repo: this is trying to run the same tests as upstream hax but I only care about what affects charon.

@ssyram
Copy link
Author

ssyram commented Sep 30, 2025

Sure, thanks!

@ssyram
Copy link
Author

ssyram commented Oct 2, 2025

Mentioned issues all resolved.

@Nadrieril Nadrieril merged commit bff544b into AeneasVerif:main Oct 2, 2025
@Nadrieril
Copy link
Member

Looks good, ty!

@Nadrieril
Copy link
Member

Nadrieril commented Oct 2, 2025

This is causing lots of panics, did you test this in charon before submitting it? We should not have merged it if it breaks charon.

@Nadrieril
Copy link
Member

Found a fix.

@ssyram
Copy link
Author

ssyram commented Oct 2, 2025

The original version (before the is_vtable_safe_method) works well with the PR AeneasVerif/charon#814 . But the later versions are not tested. I’m away from the office now.

@Nadrieril
Copy link
Member

It was indeed an incorrect invocation of is_vtable_safe_method

@ssyram
Copy link
Author

ssyram commented Oct 2, 2025

Sorry about that and thanks for the fix!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants