Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to gender neutral terms #95508

Closed
wants to merge 1 commit into from
Closed

Switch to gender neutral terms #95508

wants to merge 1 commit into from

Conversation

inclusive-coding-bot
Copy link

Hey! We noticed your repository had a few instances of gendered language. We've attempted to make the changes to gender neutral language using these substitions - joelparkerhenderson/gender-inclusive-language. These are not always perfect, but we hope they will assist maintainers in finding and fixing issues :)

You can learn more about this project and why gender neutral language matters at inclusivecoding.wixsite.com. If you have feedback for this bot, please provide it here.

@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @estebank (or someone else) soon.

Please see the contribution instructions for more information.

@rustbot rustbot added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. labels Mar 31, 2022
@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 31, 2022
Comment on lines 16 to 20
```
struct Simba {
mother: u32,
father: u32,
parent: u32,
parent: u32,
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 I don't think this will compile

Copy link
Member

@workingjubilee workingjubilee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please familiarize yourself with the limitations of CAN-SPAM and other laws restricting submitting unsolicited messages, @jamiepinheiro. I do not want you to fall afoul of international legal trouble because of a well-intentioned programming experiment.

Comment on lines +647 to +649
// The attacker wants to get directory contents deleted, to which they does not have access.
// They has a way to get a privileged Rust binary call `std::fs::remove_dir_all()` on a
// directory they controls, e.g. in their home directory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, "contribution" via regex, without human oversight, is not a good strategy. Pronouns are not context-free. It is "they do not have". I think this is the only legitimate example of something we might want to change, and it is still wrong and thus cannot be merged.

@@ -454,7 +454,7 @@ impl str {
/// assert!(v.get_mut(0..5).is_some());
/// // out of bounds
/// assert!(v.get_mut(..42).is_none());
/// assert_eq!(Some("he"), v.get_mut(0..2).map(|v| &*v));
/// assert_eq!(Some("they"), v.get_mut(0..2).map(|v| &*v));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello, @jamiepinheiro Your bot is busted. "he" is used here not as a pronoun but as a random two-character string.

@@ -980,7 +980,7 @@ pub mod fast {
unsafe fn try_initialize<F: FnOnce() -> T>(&self, init: F) -> Option<&'static T> {
// SAFETY: See comment above (this function doc).
if !mem::needs_drop::<T>() || unsafe { self.try_register_dtor() } {
// SAFETY: See comment above (his function doc).
// SAFETY: See comment above (their function doc).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many examples are just typos.

@@ -13,7 +13,7 @@ pub enum MaybeDog {

impl MaybeDog {
fn bark() {
// If this provides a suggestion, it's a bug as MaybeDog doesn't impl Groom
// If this provides a suggestion, it's a bug as MaybeDog doesn't impl Newlywed
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Groom" has other meanings, as it is also a verb, amongst other things.

@@ -7,7 +7,7 @@ pub struct Foo;
/// And then, the princess died.
//~^ ERROR missing code example in this documentation
pub mod foo {
/// Or maybe not because she saved herself!
/// Or maybe not because they saved herself!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many examples would make it contextually incorrect e.g. when there is a discussion of a hypothetical entity who IS gendered. It would require a much more careful revision.

@workingjubilee
Copy link
Member

workingjubilee commented Mar 31, 2022

This bot's modus operandi seems to be to repeatedly spam PRs until someone accepts them or blocks them, e.g.

facebook/react#24223
facebook/react#24225
facebook/react#24227

I recommend blocking both the bot and its author (one of them, anyways) so that further exercises like this one constitute block evasion. Limiting further engagement until then because its actions have also been attracting heat from random passerby, not just maintainers.

@workingjubilee workingjubilee removed T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 31, 2022
@rust-lang rust-lang locked as spam and limited conversation to collaborators Mar 31, 2022
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants