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.

Sign up for GitHub

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

Jump to bottom

It seems clang supports source-based [code coverage tool](https://clang.llvm.org/docs/SourceBasedCodeCoverage.html), if it is possible to map flow-generated code back to original code, we may not need to handle our own set of macro-based coverage tool which brings extra complicity. #948

Closed
d121122gma opened this issue Jan 12, 2025 · 0 comments
Closed

It seems clang supports source-based [code coverage tool](https://clang.llvm.org/docs/SourceBasedCodeCoverage.html), if it is possible to map flow-generated code back to original code, we may not need to handle our own set of macro-based coverage tool which brings extra complicity. #948

d121122gma opened this issue Jan 12, 2025 · 0 comments

Comments

@d121122gma
Copy link

It seems clang supports source-based code coverage tool, if it is possible to map flow-generated code back to original code, we may not need to handle our own set of macro-based coverage tool which brings extra complicity.

Originally posted by @xis19 in apple/foundationdb#11855
@OrKoN OrKoN closed this as not planned Won't fix, can't repro, duplicate, stale Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@OrKoN @d121122gma