Add @performance annotation
#274
Draft
+28
−19
Conversation
|
An example of a performance report can be seen in GitHub Actions. |
|
No clue how to read fury output but this looks great! |
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.
This introduces a new
@performanceannotation, which can be used on agenmethod definition (the same as a@debugannotation) to trigger a performance report (provided by Probably) to be displayed once at the end of compilation. A single@performanceannotation will trigger performance reporting for all derivations (by design).This PR relies on a trick suggested by
@som-snytt.Still to do: Make Probably an optional dependency of Magnolia. It should not be required in all cases.