-
Notifications
You must be signed in to change notification settings - Fork 789
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unused useSyntaxTreeCache
option
#17768
Conversation
❗ Release notes required
|
I think surface area will need an update as well. |
13b3072
to
71cfac2
Compare
The consensus is to remove it. It was also still marked experimental. |
I just noticed it's also present in VS settings. I think we should remove it there as well then :) |
(use_syntax_tree_cache) |
I think this is already done in this PR. |
Right, sorry, I somehow mis-scrolled it 🤦 Thanks! |
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.
Thanks, I think this PR can serve as a good manual on how to add / remove an option to the compiler and propagate / unpropagate it everywhere :)
Oh I know what I meant. This is still left in the resources via keywords, here. So can be removed there as well. |
Right, couldn't find anything with search in files, makes sense now :) |
Clean up.
This functionality is no longer configurable, and that cache no longer exists as a separate value in the builder.
Instead
SyntaxTree
caching occurs naturally by preservingGraphNode
computed values, IIRC.