Add idiomatic code performance and developer-facing docs to goals

[jonmeow]

• RFC topic
• Announcement topic

Most of this is addressing issue #106.

Two new explicit sub-goals:

• Idiomatic code should be performant, stemming from Changes requested to goals doc #106.
• User-facing documentation, separate thought from An incomplete, early, and in-progress overview of the language design. #83 discussion.

I think both of these are on people's minds and assumed, but still worth spelling out.

[josh11b]

new tools has a higher cost than many people appreciate." --
John Carmack

I believe should be:

new tools has a higher cost than many people appreciate."
--John Carmack

https://english.stackexchange.com/questions/28601/appropriate-dash-to-use-when-attributing-a-quotation#:~:text=Let%20a%20dash%20precede%20the,both)%20following%20a%20direct%20quotation.&text=In%20contemporary%20usage%2C%20block%20quotes,make%20the%20quotation%20stand%20out.

[jonmeow]

new tools has a higher cost than many people appreciate." --
John Carmack

I believe should be:

new tools has a higher cost than many people appreciate."
--John Carmack

https://english.stackexchange.com/questions/28601/appropriate-dash-to-use-when-attributing-a-quotation#:~:text=Let%20a%20dash%20precede%20the,both)%20following%20a%20direct%20quotation.&text=In%20contemporary%20usage%2C%20block%20quotes,make%20the%20quotation%20stand%20out.

Your reference prefers em dash (which as an aside, by https://developers.google.com/style/dashes, would have no spaces around it). This is what I was doing before #116; there, I altered the style to " -- " instead of an em dash, stemming from related conversation on the goals PR and for the reasons noted in #116 . There are spaces because I find "text--text" hard to read. Once the spaces are present, the rest is just a matter of word wrap.

[josh11b]

Higher up on that page is what I was referring to:

The source of an epigraph is usually given on a line following the

quotation, sometimes preceded by a dash. Nowhere on that page is it suggesting that there should be no whitespace between the epigraph and the source.

…

On Wed, Jul 22, 2020 at 3:07 PM Jon Meow ***@***.***> wrote: new tools has a higher cost than many people appreciate." -- John Carmack <https://twitter.com/id_aa_carmack/status/989951283900514304> I believe should be: new tools has a higher cost than many people appreciate." --John Carmack <https://twitter.com/id_aa_carmack/status/989951283900514304> https://english.stackexchange.com/questions/28601/appropriate-dash-to-use-when-attributing-a-quotation#:~:text=Let%20a%20dash%20precede%20the,both)%20following%20a%20direct%20quotation.&text=In%20contemporary%20usage%2C%20block%20quotes,make%20the%20quotation%20stand%20out . Your reference prefers em dash (which as an aside, by https://developers.google.com/style/dashes, would have no spaces around it). This is what I was doing before #116 <#116>; there, I altered the style to " -- " instead of an em dash, stemming from related conversation on the goals PR. There are spaces because I find "text--text" hard to read. Once the spaces are present, the rest is just a matter of word wrap. — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#120 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADUNHVYCB6AOXEKIDBXPES3R45PI7ANCNFSM4PFCGN2Q> .

-- Josh

[jonmeow]

Higher up on that page is what I was referring to:
The source of an epigraph is usually given on a line following the
quotation, sometimes preceded by a dash. Nowhere on that page is it suggesting that there should be no whitespace between the epigraph and the source.
…
On Wed, Jul 22, 2020 at 3:07 PM Jon Meow @.***> wrote: new tools has a higher cost than many people appreciate." -- John Carmack https://twitter.com/id_aa_carmack/status/989951283900514304 I believe should be: new tools has a higher cost than many people appreciate." --John Carmack https://twitter.com/id_aa_carmack/status/989951283900514304 https://english.stackexchange.com/questions/28601/appropriate-dash-to-use-when-attributing-a-quotation#:~:text=Let%20a%20dash%20precede%20the,both)%20following%20a%20direct%20quotation.&text=In%20contemporary%20usage%2C%20block%20quotes,make%20the%20quotation%20stand%20out . Your reference prefers em dash (which as an aside, by https://developers.google.com/style/dashes, would have no spaces around it). This is what I was doing before #116 <#116>; there, I altered the style to " -- " instead of an em dash, stemming from related conversation on the goals PR. There are spaces because I find "text--text" hard to read. Once the spaces are present, the rest is just a matter of word wrap. — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#120 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADUNHVYCB6AOXEKIDBXPES3R45PI7ANCNFSM4PFCGN2Q .
-- Josh

I think I understand what you want now, done.

[geoffromer]

This generally looks good; just a few wording suggestions.

[josh11b]

Please include the change from #126 in this as well. That is part of addressing the issues from #106.

[jonmeow]

Please include the change from #126 in this as well. That is part of addressing the issues from #106.

I've adopted #126 with edits to the phrasing based on discussion with @zygoloid about how to get this right.

[tituswinters]

nit: s/and intended/an intended/

[jonmeow]

Fixed

Proposal accepted, no new requests since

[sidney13]

Proposal accepted, decision created.