-
Notifications
You must be signed in to change notification settings - Fork 247
Document use of Unicode symbols on a per-module basis #2690
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
Comments
I definitely prefer documentation to be at top. Things at the end are a kind of 'oh, by the way' -- which works for PLFA, but not so much for Legacy: I'd say we do incremental improvements as we have time to (or have new students who need learning tasks to get going). |
I'd prefer them to be attached to the definition of the symbol itself rather than at a table at the top? |
Thanks for the swift and constructive feedback! That said, such a choice seems to leave us with only |
now it's a bit late for April Fool's, but ... have you considered using emojis in stdlib to further decrease read-, pronounce-, and writeability? |
@jwaldmann I'm not clear about the intention behind your message, but if you have specific problems with the issue, or more generally with how the library developers/maintainers contribute positively or negatively to If instead there is a problem with the way any particular person expresses themselves here, the perhaps that's something better done in private correspondence? |
sure. it was an attempt at a joke (about the appearance of stdlib, not anything personal). I have full respect for the work that goes into this project. I am sorry if the joke created to opposite impression. |
If we're going to do that then that documentation should 100% be generated by the CI When you're looking at source code your editor should already be able to tell you |
Lifted out from #2595 : rather than document symbol usage in
style-guide
, document there only the guideline that each module which introduces new (infix) Unicode symbols should document their encodings in the module where they are introduced. Cf. the didactic style adopted in PLFAFor discussion:
The text was updated successfully, but these errors were encountered: