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

RFC: Cover statement #1905

Closed
zhassan-aws opened this issue Nov 15, 2022 · 0 comments · Fixed by #1906
Closed

RFC: Cover statement #1905

zhassan-aws opened this issue Nov 15, 2022 · 0 comments · Fixed by #1906
Assignees
Labels
[C] Feature / Enhancement A new feature request or enhancement to an existing feature.

Comments

@zhassan-aws
Copy link
Contributor

This is a tracking issue for the RFC: cover_statement.

@zhassan-aws zhassan-aws added the [C] Feature / Enhancement A new feature request or enhancement to an existing feature. label Nov 15, 2022
@zhassan-aws zhassan-aws self-assigned this Nov 16, 2022
adpaco-aws added a commit that referenced this issue Jan 12, 2024
…tions (#2967)

This PR is the next step to rework/introduce the
`should_panic`/`fail_uncoverable` options as global conditions.

Until now, we haven't had a concrete proposal to do so other than the
implementation in #2532. This PR presents one for each option in their
respective RFCs. I'd like to agree on this design before starting the
code review for #2532.

Related to #1905 #2272 #2299 #2516
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[C] Feature / Enhancement A new feature request or enhancement to an existing feature.
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant