Fair point, I'll give it a go to see for myself, thanks.
Alternative, if it's web calls then openAPI and a specific generator will work faster long term... (write generator once then import swagger files for whatever you need or tell claude to generate the swagger if not available?)
That would help with api changes longer term (just update swagger file, regen code and update where needed)
If it's actual library calls (C/C++), then why would wrapper be needed?, doesn't add yet-anothet-layer that makes things more difficult to grasp?
I am mostly coding with ruby so I constantly find myself wrapping APIs or Linux tools to get things done faster.
Usually I just send a link to the API doc with a sentence or two to let it wrap one or two functions leading to small, specialized and mostly efficient wrappers without overhead. Easy to fix should something change.
It's just a random aspect where I find AI to work really well for coding (for me).
Alternative, if it's web calls then openAPI and a specific generator will work faster long term... (write generator once then import swagger files for whatever you need or tell claude to generate the swagger if not available?)
That would help with api changes longer term (just update swagger file, regen code and update where needed)
If it's actual library calls (C/C++), then why would wrapper be needed?, doesn't add yet-anothet-layer that makes things more difficult to grasp?