Skip to content

About

Open-Source Functional Programming Language Design Textbook

Resources

Stars

3 stars

Watchers

1 watching

Forks

Latest commit

 

History

79 Commits

Folders and files

Repository files navigation

Mathcha Illustrations: https://www.mathcha.io/editor/5EgegIYniVvh6M9jj3tjYvExpfYrvkPzfD3ZyZ8

YouTube: https://www.youtube.com/@ConciseWorksYT

Contributing

Anyone is welcome to contribute. Just fork the repository, once edits are complete, submit a pull-request.

Guidlines:

Don't

  1. Do not use words like "trivially, obviously, clearly" as if it were, there would be no need to state such. The only exceptions of the word "trivial" are when referring to the "trivial" solution of a problem. That is, when the problem is by definition solved by a base case.
  2. Do not open sentences with "to which we mean" or "and for that matter we can say." Instead keep text dry, say "I.e.," or "then."
  3. Do not skip steps (no stone left unturned).
  4. Do not write blocks of text. If you reach 3 blocks, it either must be crucial or must be reworded.
  5. Reframe from indentations. Only use on subsequent paragraphs of a large piece of text. I.e., the first paragraph is always left with no indentations.
  6. Following from 5., formatting is more about how visually digestable text is, rather than conventional standards of writting.
  7. Do not break Theorem boxes between pages. If your text is too large, break it into parts.
  8. Put non-critical information into Tip boxes
  9. Put some-what critical information into Note boxes
  10. Reframe the use of personal pronouns.

Goal

Text books should operate as dictionaries of knowledge, not stories or a displays of skill. Things ought to be consise and well written, so much so, that a laymen could understand at a highlevel what each definition or theorem means.

About

Open-Source Functional Programming Language Design Textbook

Resources

Stars

3 stars

Watchers

1 watching

Forks

Releases

Packages

Contributors

Languages