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

Move documentation of kani_core modules to right places #3851

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

qinheping
Copy link
Contributor

Resolves #3815

Documentations of kani_core modules doesn't show up correctly on https://model-checking.github.io/kani/crates/doc/kani/mem/index.html. This PR move the comments to the right place so that they will show up correctly.

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

@qinheping qinheping requested a review from a team as a code owner January 24, 2025 09:12
@github-actions github-actions bot added the Z-BenchCI Tag a PR to run benchmark CI label Jan 24, 2025
Copy link
Contributor

@carolynzech carolynzech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of deleting the documentation from each of the files, can you keep a sentence or two about what they do, and then refer to the new location of the docs for full details? I agree that our full docs should be visible to our users, but for internal development, it's still useful to have some comments at the top of the file explaining what it does. For example, in kani_core::mem, can you add a sentence back like "This module contains functions useful for checking unsafe memory accesses. For full documentation, see lib.rs"?

(Also, were you able to test this at all to demonstrate that these moves fix the problem?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Z-BenchCI Tag a PR to run benchmark CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing items in the documention for the mem module
2 participants