Verify that macros do work without any imports#3188
Merged
Conversation
lifthrasiir
force-pushed
the
test-no-imports
branch
from
b0ef56b to
c2d4e8a
Compare
Member
|
Great find with a principled solution! I agree that this should be part of 0.19.0. bors r+ |
Member
|
Agreed, thanks! |
Merged
Contributor
|
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Currently virtually all (positive) tests import
pyo3::prelude::*, making it hard to detect a certain class of bugs. This PR adds an explicit test that never imports frompyo3to fix this.Also this fixes a minor bug from #3157 which didn't work without
use pyo3::types::PyType;. I think this should be a part of 0.19.0 (#3187), so no additional changelog would be required (as this feature is new in 0.19.0).