Maybe I'm using it wrong, but it's way less cognitive overhead for me to just type for for x,y := range something {} than it is to try and prompt "Iterate over this list of values...etc."
I'd say that prompting "Iterate over this list of values...etc." is definitely using it very wrong (autocomplete should more or less handle that sort of thing anyway). Prompts should be more in line with "write a C++ function that can parse XML files that look like this (upload a few sample files) and return the data in this struct (copy and paste struct from your header file)" followed by "write a set of unit tests for this function". You then check that the unit tests look reasonable, add any other things you feel you should test for, make sure the generated code passes the unit tests, and then check it in.
I'd say that prompting "Iterate over this list of values...etc." is definitely using it very wrong (autocomplete should more or less handle that sort of thing anyway). Prompts should be more in line with "write a C++ function that can parse XML files that look like this (upload a few sample files) and return the data in this struct (copy and paste struct from your header file)" followed by "write a set of unit tests for this function". You then check that the unit tests look reasonable, add any other things you feel you should test for, make sure the generated code passes the unit tests, and then check it in.