Implemented Lazy[T], Documentation changes, etc #82
Conversation
This file contains 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
krux02
pushed a commit
to krux02/Nim
that referenced
this pull request
Jan 11, 2022
82: compiler analysis tracing debugutils r=haxscramper a=saem This should easy testing and allow people to learn how the compiler does things by applying tracing to sections of code. A rather clever usage is to apply this to various parts of the test spec. - use `addInNimDebugUtils` or create a specialized one for a proc you want to trace - use `nimCompilderDebugRegion` along with the `nimDebugUtils` define in order to get traces for regions of code - learn how the compiler does things... or doesn't as the case maybe system has a template `nimCompilerDebugRegion` which is available when compiling with `nimDebugUtils` defined. use this template as a block and all code under it will then emit debug trace output from semExpr and a number of other key procs within the compiler. spam is kept to the point by creating delta stacktraces and nested (indented) rendering of messages is used to convey the recursive nature of this process. the tracing facility is templatized and can be extended to add output for additional situations if the present hooks do not suffice. as part of this work the debugutils module was heavily gutted as it was overwraught. there was an extension made to the compiler config to track a small seq for delta stacktrace and output indentation tracking. backstory: - started with existing debugutils module, but it was over engineered - removed most of the code and instead have a template to inject tracing Future improvements: - messages themselves need some love - more things need traces Co-authored-by: Saem Ghani <saemghani+github@gmail.com>
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
* Also added 'containsHandler' to events.nim
I don't know why the koch changes are included in this though.