Examples of feminine pronouns used for abstract subjects

This section is empty…

Colorado DoT — Getting a License

https://www.codot.gov/safety/colorado-teen-drivers/parent/driver-education.html

The steps required to get a license vary depending upon when a teen starts the process. If

unimplemented! (underline){:type "underline", :contents-begin 389, :contents-end 392, :position {:start {:line 12, :column 93, :offset 388}, :end {:line 12, :column 98, :offset 393}}, :children ("her")}
goal is to get her license on her 16th birthday,
unimplemented! (underline){:type "underline", :contents-begin 444, :contents-end 450, :position {:start {:line 12, :column 148, :offset 443}, :end {:line 12, :column 156, :offset 451}}, :children ("she’ll")}
need to start driver’s ed at age 14 ½. Generally speaking, some sort of classroom-based education is required before a teen can obtain a drivers permit. Once
unimplemented! (underline){:type "underline", :contents-begin 611, :contents-end 614, :position {:start {:line 12, :column 315, :offset 610}, :end {:line 12, :column 320, :offset 615}}, :children ("she")}
has a permit,
unimplemented! (underline){:type "underline", :contents-begin 631, :contents-end 634, :position {:start {:line 12, :column 335, :offset 630}, :end {:line 12, :column 340, :offset 635}}, :children ("she")}
will need to log 50 hours of drive-time over the course of one year before applying for a license.

Emacs — completing-read docstring

completing-read

  • confirm-after-completion means that the user can exit with any input, but

    unimplemented! (underline){:type "underline", :contents-begin 919, :contents-end 922, :position {:start {:line 20, :column 77, :offset 918}, :end {:line 20, :column 82, :offset 923}}, :children ("she")}
    needs to confirm her choice if
    unimplemented! (underline){:type "underline", :contents-begin 956, :contents-end 959, :position {:start {:line 20, :column 114, :offset 955}, :end {:line 20, :column 119, :offset 960}}, :children ("she")}
    called minibuffer-complete right before minibuffer-complete-and-exit and the input is not an element of COLLECTION.

I love profunctors. They're so easy.

https://www.schoolofhaskell.com/school/to-infinity-and-beyond/pick-of-the-week/profunctors

This was part of the user-facing code we used in production that lets the user adjust various parameters:

unimplemented! (underline){:type "underline", :contents-begin 1345, :contents-end 1348, :position {:start {:line 28, :column 107, :offset 1344}, :end {:line 28, :column 112, :offset 1349}}, :children ("she")}
can either click an up/down button—or supply a new value directly. The check function then validates the new input with respect to the old.

GHC contributor's wiki — Coding Style

https://gitlab.haskell.org/ghc/ghc/-/wikis/commentary/coding-style#21-notes-the-basic-idea

When writing code, there is often a moment when a careful programmer will mentally say something like "This data type has an important invariant".

unimplemented! (underline){:type "underline", :contents-begin 1800, :contents-end 1803, :position {:start {:line 36, :column 148, :offset 1799}, :end {:line 36, :column 153, :offset 1804}}, :children ("She")}
is faced with two choices, both unsatisfactory.
unimplemented! (underline){:type "underline", :contents-begin 1854, :contents-end 1857, :position {:start {:line 36, :column 202, :offset 1853}, :end {:line 36, :column 207, :offset 1858}}, :children ("She")}
can add the invariant as a comment, but that can make the data type declaration too long, so that it is hard to see what the constructors are. Alternatively,
unimplemented! (underline){:type "underline", :contents-begin 2018, :contents-end 2021, :position {:start {:line 36, :column 366, :offset 2017}, :end {:line 36, :column 371, :offset 2022}}, :children ("she")}
can document the invariant elsewhere, and risk it going out of date. Over twenty years, everything goes out of date!

numeric-prelude — Readme

https://hackage.haskell.org/package/numeric-prelude-0.4.4#readme

In some cases, the hierarchy is not finely-grained enough: Operations that are often defined independently are lumped together. For instance, in a financial application one might want a type "Dollar", or in a graphics application one might want a type "Vector". It is reasonable to add two Vectors or Dollars, but not, in general, reasonable to multiply them. But the programmer is currently forced to define a method for (*) when

unimplemented! (underline){:type "underline", :contents-begin 2693, :contents-end 2696, :position {:start {:line 44, :column 432, :offset 2692}, :end {:line 44, :column 437, :offset 2697}}, :children ("she")}
defines a method for (+).

A Guide to Writing Mathematics

[cite:@lee2010guide]

Mathematicians actually spend a great deal of time writing. If a mathematician wants to contribute to the greater body of mathematical knowledge,

unimplemented! (underline){:type "underline", :contents-begin 2969, :contents-end 2972, :position {:start {:line 53, :column 62, :offset 2968}, :end {:line 53, :column 67, :offset 2973}}, :children ("she")}
must be able communicate her ideas in a way which is comprehensible to others.

Justify text with HTML/CSS? Don’t do it!

[cite:@kadavy2014justify]

Those “jagged” text block edges that text-justifiers are trying to get rid of actually make the text easier to read. Besides the obvious reason that big gaps between words interrupt the reading flow, there’s a less obvious reason. While the reader’s eye is scanning each line, it’s easier for

unimplemented! (underline){:type "underline", :contents-begin 3445, :contents-end 3448, :position {:start {:line 62, :column 294, :offset 3444}, :end {:line 62, :column 299, :offset 3449}}, :children ("her")}
to find the next line if the lines are of uneven length. This is especially true for dyslexic readers.

Emacs source code

Source code for describe-function-1. 

;; Avoid asking the user annoying questions if she decides
;; to save the help buffer, when her locale's codeset
;; isn't UTF-8.

Guile Scheme documentation

https://www.gnu.org/software/guile/manual/html_node/Guile-Implementation.html

At some point, after one has been programming in Scheme for some time, another level of Scheme comes into view: its implementation. Knowledge of how Scheme can be implemented turns out to be necessary to become an expert hacker. As Peter Norvig notes in his retrospective on PAIP36, “The expert Lisp programmer eventually develops a good ‘efficiency model’.”

By this Norvig means that over time, the Lisp hacker eventually develops an understanding of how much

unimplemented! (underline){:type "underline", :contents-begin 4371, :contents-end 4374, :position {:start {:line 82, :column 103, :offset 4370}, :end {:line 82, :column 108, :offset 4375}}, :children ("her")}
code “costs” in terms of space and time.

This chapter describes Guile as an implementation of Scheme: its history, how it represents and evaluates its data, and its compiler. This knowledge can help you to make that step from being one who is merely familiar with Scheme to being a real hacker.