Add documentation for new features #185
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add --debug - Remove -R files Signed-off-by: John Pennycook <[email protected]>
Signed-off-by: John Pennycook <[email protected]>
Signed-off-by: John Pennycook <[email protected]>
Divergence is no longer the only metric calculated by CBI, and we can now measure and visualize platform coverage. Signed-off-by: John Pennycook <[email protected]>
Signed-off-by: John Pennycook <[email protected]>
For now, this is not a full tutorial. I would like to collect more feedback from users about how often they encounter this functionality before spending more time writing a complete tutorial for it. Signed-off-by: John Pennycook <[email protected]>
laserkelvin
approved these changes
Apr 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issues
N/A
Proposed changes
cbi-covandcbi-tree).cbi-treeinto the tutorial in relevant places, to highlight that it exists.As it says in the commit history, I'm reluctant to write a full-fledged tutorial for custom compiler behavior at this point. The tutorial we have right now is really a quickstart guide, and I'm hoping that most users won't have to define really complicated custom behaviors to get meaningful results. But I've added a note that people should file an issue if I'm wrong.
If it turns out that we need a better tutorial or more documentation for this feature, I think we can always do this after 2.0.0 releases. There's no reason that we can't update the documentation independently.