This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
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.
don't allow ? in non-result v2 benchmark function defs, require either Result or () return type #13277
don't allow ? in non-result v2 benchmark function defs, require either Result or () return type #13277
Changes from all commits
546bc07
bab6509
592b1af
6c5d509
e328401
4da0b86
8fed25a
3aaa638
d707202
7d567bc
b8def3c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think its good to have the syntax clarification, but not sure if this check here actually works.
It would still be possible to just
return Err("".into())
instead of using?
and it would exclude#[block]
s from using it.I dont think we can/have to explicitly check this, or?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could have a visitor that checks all return statements and applies a
static_assertions::assert_type_eq_all!
check to each one verifying that it is compatible withBenchmarkResult
, and that wouldn't be too hard, but honestly now thatBenchmarkResult
is so short I am leaning towards just requiring-> BenchmarkResult
on all benchmark function defs, which would greatly simplify things and wouldn't be a very heavy lift. Thoughts?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Either way would work though I think