Add crate:: prefix to top-level wildcard imports #302
Merged
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
docs.rs failed to build `ndarray-linalg` 0.14.0. The [build log](https://docs.rs/crate/ndarray-linalg/0.14.0/builds/412464) seems to indicate that this change will fix the issue.
Codecov Report
@@ Coverage Diff @@
## master #302 +/- ##
=======================================
Coverage 90.71% 90.71%
=======================================
Files 71 71
Lines 3726 3726
=======================================
Hits 3380 3380
Misses 346 346 Continue to review full report at Codecov.
|
|
https://docs.rs/ndarray-linalg/0.14.1-alpha.1/ndarray_linalg/ |
termoshtt
added a commit
that referenced
this pull request
Aug 14, 2021
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.
docs.rs failed to build
ndarray-linalg0.14.0; see #301. The build log seems to indicate that this change will fix the issue, although I'm not able to reproduce the original issue locally, so I'm not entirely sure this will fix it.