Skip to content

[DRAFT] Resolve stubs and contracts in trait implementations #4130

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

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

carolynzech
Copy link
Contributor

@carolynzech carolynzech commented Jun 4, 2025

This PR is not ready for review; I am testing that it passes CI before writing tests.

Resolves #4084
Resolves #4057

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

@github-actions github-actions bot added the Z-EndToEndBenchCI Tag a PR to run benchmark CI label Jun 4, 2025
@carolynzech carolynzech force-pushed the contracts-qualified-paths branch from 5d20982 to 396dfd0 Compare June 5, 2025 20:12
@carolynzech carolynzech self-assigned this Jun 5, 2025
@carolynzech carolynzech force-pushed the contracts-qualified-paths branch 6 times, most recently from e3edb88 to b2dfdb5 Compare June 10, 2025 12:57
the attribute lifetime is tied to TyCtxt, so we should make that explicit
…ct_attribute` to call `resolve_fn_path`

and thereby be able to resolve qualified paths, which they can't do in the current impl because `resolve_from_mod` only handled simple paths
@carolynzech carolynzech force-pushed the contracts-qualified-paths branch from b2dfdb5 to 801158c Compare June 26, 2025 17:55
@github-actions github-actions bot added the Z-CompilerBenchCI Tag a PR to run benchmark CI label Jun 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Z-CompilerBenchCI Tag a PR to run benchmark CI Z-EndToEndBenchCI Tag a PR to run benchmark CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Kani not resolving qualified paths in verify-std Investigate why contracts don't use resolve_fn_path
1 participant