AI PoC workaround-for-stack-overflow reworks [do not merge]#217
Draft
AI PoC workaround-for-stack-overflow reworks [do not merge]#217
Conversation
Coverage Report
Compared to |
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
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 a quickly drafted branch with AI tooling assisted PoC for the stack overflow issue. Good for quick tryouts, but we probably shouldn't merge it (at least as-is).
The idea is unwind the recursion into a manually managed stack to avoid being limited by the system thread's stack size.
Use commit filtering on Github to review - the first two commits just move the tests out of
Ctrl+Fscope so it's possible to navigate the code quickly and find fn uses manually.