don't bring in the fastcpy_unsafe module with safe-* features
#150
Conversation
This file contains 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
No functional changes intended. This makes it build successfully in an environment with `--deny=unsafe_code`, e.g.: ``` RUSTFLAGS=--deny=unsafe_code cargo build ```
krasimirgg
changed the title
fastcpy_unsafe module when with safe-* featuresfastcpy_unsafe module with safe-* features
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #150 +/- ##
==========================================
+ Coverage 89.00% 89.20% +0.19%
==========================================
Files 12 12
Lines 2484 2465 -19
==========================================
- Hits 2211 2199 -12
+ Misses 273 266 -7 ☔ View full report in Codecov by Sentry. |
|
Can you rebase? I fixed the nightly build in another PR |
|
Thanks! released with |
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.
No functional changes intended.
This makes it build successfully in an environment with
--deny=unsafe_code, e.g.: