I've simply never had an issue with this sort of thing in months of using co-pilot to be my fancy autocomplete. And if there was an issue I'd notice quickly enough, because I am still the primary pilot.
It is also great as a starting point for error messages, comments, etc.
I think the key is to still give a shit about the code you're writing.
My rule using copilot is to use it as a fancy typing assistant which will frequently make mistakes - so you need to read everything it writes for you, and have solid test coverage too in order to avoid accidentally accepting a dumb mistake.
And much more enjoyable. I haven’t tried Copilot yet, but the process of letting it generate something and then checking it for accuracy sounds mind-numbing and stressful. Kind of like supervising a car that’s on assisted cruise: I don’t enjoy that either.
Do you use it to write anything you want - even works on READMEs and comments! But like any good test - test it in a different way to how to implement it.
It is also great as a starting point for error messages, comments, etc.
I think the key is to still give a shit about the code you're writing.