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

Make convert_symbolizedresults_to_c() safe #307

Merged

Conversation

danielocfb
Copy link
Collaborator

There is nothing unsafe about the convert_symbolizedresults_to_c() function. Remove the unsafe attribution.

There is nothing unsafe about the convert_symbolizedresults_to_c()
function. Remove the `unsafe` attribution.

Signed-off-by: Daniel Müller <[email protected]>
@codecov
Copy link

codecov bot commented Sep 8, 2023

Codecov Report

Patch coverage: 100.00% and project coverage change: -3.92% ⚠️

Comparison is base (a995b7b) 89.22% compared to head (60d7c6a) 85.30%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #307      +/-   ##
==========================================
- Coverage   89.22%   85.30%   -3.92%     
==========================================
  Files          37       37              
  Lines        4657     4654       -3     
==========================================
- Hits         4155     3970     -185     
- Misses        502      684     +182     
Files Changed Coverage Δ
src/c_api/symbolize.rs 70.90% <100.00%> (-23.94%) ⬇️

... and 4 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@danielocfb danielocfb merged commit 0dbf152 into libbpf:main Sep 8, 2023
22 checks passed
@danielocfb danielocfb deleted the topic/convert_symbolizedresults_to_c-safe branch September 8, 2023 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants