Conversation
TiagoCavalcante
approved these changes
Feb 21, 2022
Contributor
TiagoCavalcante
left a comment
TiagoCavalcante
left a comment
There was a problem hiding this comment.
LGTM - good idea!
Member
|
This had occurred to me a while ago and I think it is a good idea. But can we just make add it as an option to the exisiting $TraceEvaluation? |
Member
|
Looks great now - thanks for doing! |
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
3 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.
Trying to understand the problem in #154, I realized that it would be useful to record how long each evaluation step takes, so here is a PR that implements that.