e9ec0ab695
This pull request attempts to fix major inconsistencies and some incorrect information. It also streamlines the article by rearranging and/or removing stubs of information. - Replaced `v` and `^` set operators with cup and cap, respectively; - Removed history section as the information was not necessarily accurate; - Expanded symbols section by splitting it into operators and qualifiers; - Renamed "builtin sets" to "canonical sets"; - Replaced Latin alphabet symbols for canonical sets with their Blackboard bold variants (see: https://en.wikipedia.org/wiki/Blackboard_bold); - Rewrote set relations section to streamline information; - Rewrote examples in set operations section to make meaning more clear; - Removed generalized operations section, as the original author was clearly trying to typeset unions and intersections of collections of sets, but the notation is impossible to replicate in markdown and only makes the section more unclear.
Learn X in Y minutes
Whirlwind tours of (several, hopefully many someday) popular and ought-to-be-more-popular programming languages, presented as valid, commented code and explained as they go.
We need YOU!...
... to write more inline code tutorials. Just grab an existing file from this repo and copy the formatting (don't worry, it's all very simple). Make a new file, send a pull request, and if it passes muster I'll get it up pronto. Remember to fill in the "contributors" fields so you get credited properly!
Contributing
All contributions are welcome, from the tiniest typo to a brand new article. Translations in all languages are welcome (or, for that matter, original articles in any language). Send a pull request or open an issue any time of day or night.
Please prepend the tag [language/lang-code] to your issues and pull
requests. For example, [python/en] for English Python. This will help
everyone pick out things they care about.
We're happy for any contribution in any form, but if you're making more than one major change (i.e. translations for two different languages) it would be super cool of you to make a separate pull request for each one so that someone can review them more effectively and/or individually.
For a detailed style guide, please review the full CONTRIBUTING guidelines.
License
Contributors retain copyright to their work, and can request removal at any time. By uploading a doc here, you agree to publish your work under the default Creative Commons Attribution-ShareAlike 3.0 Unported licensing included on each doc page.
Anything not covered by the above -- basically, this README -- you can use as you wish, I guess.