You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've based our style guide on this Swift style guide (thank you to the maintainers and all the contributors, btw) so while figuring out how to address the use of exclusionary language in our style guide I came here to see if I could find inspiration. Since I don't see anything in this style guide or any recent issues I'd like to prompt a discussion -- would it make sense to add style rules for avoiding exclusionary language to the naming discussion in the style guide or perhaps to its own section of the document?
Thanks for bringing this issue up. RW has embraced the notion of getting rid of exclusionary language in books and articles. I can see for starters that the main branch needs to be renamed. The guide could perhaps start by making a reference to the link you provided.
We've based our style guide on this Swift style guide (thank you to the maintainers and all the contributors, btw) so while figuring out how to address the use of exclusionary language in our style guide I came here to see if I could find inspiration. Since I don't see anything in this style guide or any recent issues I'd like to prompt a discussion -- would it make sense to add style rules for avoiding exclusionary language to the naming discussion in the style guide or perhaps to its own section of the document?
For context, I mean exclusionary language in the way it is used in this Apple Developer news item: https://developer.apple.com/news/?id=1o9zxsxl
The text was updated successfully, but these errors were encountered: