Oof. LGPL. That "time saver" will infect your entire codebase and open your company to sizable liability.
Even if they're never sued, companies will do internal OSS scans to limit their risks which would catch this. The result would be (at minimum) a talking to for the dev who committed it, and developer time spent doing a clean room re-write.
And then I will download a trial of the resulting binary, and send a GPL compliance letter to the company. Unless they took care to use dynamic linking in the LGPL case, they are legally obliged to send me the source code under the license, so I can release it all as FOSS under that license.
Then I contact the copyright holder (or one of the many, in case of e.g. the Linux kernel). They probably care, or else they would not use the GPL. I also believe there are organizations that can help such as the Software Freedom Conservancy.
Ok, 3 tweets where someone has coaxed copilot into reproducing some copypasta for clout.
That's just not likely in any real use of copilot since it is typically completing single lines, using the variables and patterns which occur in the file that is being edited.
Anybody who had actually used it for work would know that these contrived examples are irrelevant.
Even if they're never sued, companies will do internal OSS scans to limit their risks which would catch this. The result would be (at minimum) a talking to for the dev who committed it, and developer time spent doing a clean room re-write.