-
Notifications
You must be signed in to change notification settings - Fork 263
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
Recursive function analysis #13
Comments
Hi! While this is a good idea on paper, I think that going into functions recursively could be a little dangerous, especially when you get into the STL and the like where the rabbit hole can turn out to be pretty deep. It would be easy to have OpenAI costs spiral out of control for users. |
Re JusticeRage, |
Correct, because the comments added during the first request help davinci-003 provide better suggestions for variable names. |
I've experimented manually with this and have gotten great results. Knowing what the called functions do help the model see the big picture and understand better the function. You could add the analysis for the called functions as a comment before it is called and then pass it whole to the model, without displaying it to the user. |
This is definitely something I intend to look into in the near future. |
Hi JusticeRage,
I was trying your tool, and first I found it super easy to use. Then, I got a little idea to improve a bit the analyze. When the current function calls others tiny functions without other calls inside, I think it will be great to first request analyze for the tiny one and rename it. Especially since it doesn't seem to be too wrong when it suggests a name for small functions. Then with some functions name filled, GPT-3 do a better job.
If you think the idea is good, I can make a pull request this week.
The text was updated successfully, but these errors were encountered: