I prototyped much of this code using ChatGPT and Copilot. I won't go so far as to say, "I couldn't have done it without you, ma!", but it certainly would have t

I prototyped much of this code using ChatGPT and Copilot. I won't go so far as to say, "I couldn't have done it without you, ma!", but it certainly would have taken me much longer. In terms of learning the actual API, they were worth their weight in gold. One trick to use is that Copilot can read up to (apparently) 20 other tabs that you have open. So, I will open the source code containing the API methods I need in my other tabs and close everything else. > The working code for insertion of the check_invariants statements was a stroke of dumb luck after 15 hours, from one of the suggestions given by Github Copilot. What is funny here is that it suggested something radically different. I was going down the rabbit hole I chronicled here: https://stackoverflow.com/questions/74964153/gcc-gimple-c-api-how-to-insert-a-call-to-a-member-function-from-another-memb https://stackoverflow.com/questions/74964153/gcc-gimple-c-ap... One strategy I use in unfamiliar territory is to repeatedly generate the set of 10 Copilot suggestions and see if anything sticks out. I had gone through maybe 3-4 rounds when it spits out one that looks nothing like what I currently have. I try that suggestion, and it works. I shake my head. What the fuck. Alright, I'll take it. It wanted to do a regular C-style call that had no member namespace, which by sheer luck happens to work due to how C++ lookup works.