additional terms

[moimikey]

Hi,

I'd be more than happy to submit some pull requests on these various terms. I'd much rather get an opinion first before starting on a PR:

• [ ] application (as a compliment to partial application)
• [ ] thunk
• [ ] tail-call optimization
• [ ] trampolines
• [x] functor
• [ ] reducer
• [ ] transducer
• [ ] homomorphism

[hsavit1]

@moimikey - this would be a fantastic if you could define these!

I would add natural transformations and morphisms as well to this list

[moimikey]

awesome. will do :+1:

[moimikey]

@hsavit1 there's that fine line between functional programming paradigms and concepts that we use daily, vs. all and everything under category theory. this list could grow or get chopped down. i'll obviously crop and add and crop some more:

• [ ] morphisms
  • [ ] homo-
  • [x] iso-
  • [ ] mono-
  • [ ] epi-
  • [ ] bi-
  • [x] endo-
  • [ ] auto-
  • [ ] natural transformation

[hsavit1]

@moimikey agreed, we wouldn't want to "scare" anyone away from functional programming with overwhelming dictionary of category theory terms (and no examples)

on the other hand, I'd love to educate more programmers on category theory concepts. They were insanely helpful for me when learning Haskell for the first time.

[hemanth]

@moimikey Sorry for the late reply, please feel free to do the PRs!

Thank you!

[jethrolarson]

Functor is already in.

This is turning into a dictionary fast but maybe that's still okay. Some of the topics kind of deserve their own pages. Especially when it comes to defining why they're useful. I could see a page dedicated to morphisms.

It's hard to summarize monad in a paragraph and one or two examples don't illuminate, for example.

[hemanth]

@jethrolarson We could start a wiki in this repo, maybe?

[hemanth]

@jethrolarson Interested?

[flip111]

polymorphism

[stereobooster]

immutability and functional data structures

[hemanth]

profunctors as well.

[stereobooster]

totality e.g. no effects at all. Exceptions and divergence as effects, but not side effects, e.g. "pure" function can have it. And side effects is IO and non-determinism.

[stereobooster]

scopes as soon as programing language has symbols it has to deal with scopes. Basically it can ignore them and make one global scope. Or choose functions as scopes and visibility of higher-call stack scopes (hello closures). Or lexical scopes, or module scopes. It is also to choose different models of scopes for different types of symbols.

Language without symbols - simple lambda calculus. One global scope - lambda calculus extended with symbols or assembly language.

[tfausak]

Thanks for the great resource! Is this where I can report bugs on this post? If so:

• The titles don't define anchors (like <h2 name="...">), so the links in the table of contents don't go anywhere.
• One of the paragraphs in the "Closure" section isn't formatted properly.

[jethrolarson]

functional.works-hub.com is not maintained by this repo. They copied the readme and didn't compile the markdown properly. I'm not sure who you should bug.