VGhlcmUgaXMgbm8gZ2VudWluZSBpbnRlbGxpZ2VuY2UgLCB0aGVyZSBpcyBhcnRpZmljaWFsIHN0dXBpZGl0eS4NClRoZXJlIGlzIG5vIHNlcmVuaXR5LCB0aGVyZSBpcyBhbnhpZXR5Lg0KVGhlcmUgaXMgbm8gcGVhY2UsIHRoZXJlIGlzIHR1cm1vaWwuDQpUaGVyZSBpcyBubyBzdHJ1Y3R1cmUsIHRoZXJlIGlzIHBvcnJpZGdlLg0KVGhlcmUgaXMgbm8gb3JkZXIsIHRoZXJlIGlzIGNoYW9zLg==

  • 0 Posts
  • 5 Comments
Joined 9 months ago
cake
Cake day: May 14th, 2024

help-circle




  • Really? Maybe my variable names and column headers were sufficiently obscure and technical that I didn’t run into these issues about a month ago. Didn’t have any problems like that when analyzing census data in R and made Copilot generate most of the code.

    Is this one of those US exclusive things?

    I definitely did refer to various categories such as transgender or homosexual in the code, and copilot was ok with all of them. Or maybe that’s the code I finally ended up with after modifying it. I should run some more tests to see if it really is allergic to queer code.

    Edit: Made some more code that visualizes the queer data in greater detail. Had no issues of any kind. This time, the inputs to Copilot and the code itself had many references to “sensitive subjects” like sex, gender and orientation. I even went a bit further by using exact words for each minority.