But also, it can reasonably set types for the inputs of say a React component, just based on an example (made up) usage of some props you give it. And you can even, if you are very uncouth, simply generate the sensible props for a certain kind of object given a description by say the user.
It can do things like generate controlled form state management etc, which was quite error-prone to do with macros when things get complicated.
It can summarize commits for documented code accurately too, especially if you comment what you've done for some reason or another. This saves a good 2-3 minutes an hour I didn't know I could save, for the average of say 1-2 commits I'd do usually per hour.
Notably GPT-4 is needed to do these consistently well.
There are sometimes tools available for this, but the nice thing about ChatGPT is that it's effectively a single tool that can be used for any reasonably well-known API framework in any language.
I could see it generating out an openapi file but there are already so many templates out there to start from it does not make sense to use ai for this, in my opinion.
Another example could be that you would really like to use macros/templates for something, but you can't due to external requirements, like Unreal Header Tool being unable to parse those if you want to export your classes to the engine. So you get to write the same code multiple times for different types. Amazing!
So the AI gets the benefit of having a template without the trouble of getting someone to make and maintain each one.
Would be better to ask ai to generate the templating library.
Doing it for a mapping feels like a deficiency in the code unless chatgpt is putting thoughts behind the variable names and reasoning about what mapping makes the most sense.