You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't my repository so it isn't my place to say but for what it's worth, docstrings (documentation) are for contextualizing why X or Y function / class is important or point out any risks or input assumptions, etc, or just reasons to use the function.
The linked demo shows auto-created docstrings that simply restate what the code is already doing. A docstring like that is something that you could learn just from reading the source code, itself. IMO such docs are worse than none at all because at least if a docstring is missing, linters like pydocstyle can point out where documentation is lacking so programmers can go back in and improve them.
It'd be a different story if the auto-generated text gave actual insights about the code though. Since neogen uses snippet expansion engines, I could see a use-case where, say, you have a function like:
deffoo(bar, fizz, buzz=tuple()):
"""Do blah, I am a description, written by a human. Args: bar (SomeClass): |Your cursor is here| fizz ([TODO:parameter]): [TODO:description] buzz ([TODO:parameter]): [TODO:description] """foriteminbuzz:
# ...
And, using an AI, give it an automated prompt like "given 1. the entire function body and 2. the manually written description, "Do blah, I am a description, written by a human." and 3. SomeClass type, suggest a description for the fizz parameter because that's where my cursor is currently positioned"
A thing like that might be useful. But anyway, this is borderline AGI territory, IMO.
like this: https://github.com/mintlify/writer
The text was updated successfully, but these errors were encountered: