feat(test2): Provide a #[test] macro
#135
Merged
+1,079
−77
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.
This is part of #13
I went with
ctorbecauselinkme, see nvzqz/nvzqz/divan/pull/32divan#32Like
ctors optional proc-macro, I kept out proc-macro minimal to experiment with what it might take to use declarative attributes when they are ready.I put
TESTSregistry of all tests in callers crate via#[libtest2::main]to simulate the lack of cross-crate registration which is the initial proposal for rust-lang/testing-devex-team#3. If we had cross-crate registration, we could instead expose apub fn main() {}that people could import and not need#[libtest2::main]at all. We could experiment with putting it in a prelude.Known issues:
()is allowed as a return type#[should_panic]#[ignore]