3 ms·
Hmm I think someone else has voiced a similar opinion on the wording here, and I actually do agree with you. What was meant by this statement is really just ta
by akshaysg 2y ago
Hmm I think someone else has voiced a similar opinion on the wording here, and I actually do agree with you.
What was meant by this statement is really just taking care of plumbing and the visualization of how code relates to one another.
To give you a very basic/silly example of plumbing, if I add a parameter in a function used in 100s of places, doing the manual work to figure out what edits I need to make to those callers is pretty annoying and in most cases mechanical.
If you're lucky, you can do a grep + replace (or just use a default param), but in most cases I find it requires more manual intervention than that.
- gavmor 2y agoAdding a parameter to the function signature, and then passing an additional value at each call site is done... automatically in Haystack? Impossible! Edit: And "to figure out what edits I need to make" is done by any ol' compiler, no?
- akshaysg 2y agoNot yet -- it's our vision to automate stuff like that! > Edit: And "to figure out what edits I need to make" is done by any ol' compiler, no? Kinda? There are cases where you have to drill data down into the callstack (i.e. pass data from above). There are folks who have gone down this path before: https://www.jetbrains.com/help/resharper/Refactorings__Change_Signature.html#call_tree https://www.jetbrains.com/help/resharper/Refactorings__Chang... but we intend to automate it even more and show it to the user in an organized way for them to handle large-scale "refactors".