Difference between revisions of "Don't fear the Monad"
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
=[[Monoid]] helps to guarantee you to build a software with [[one and only one type]] ...(start at 1296)= | =[[Monoid]] helps to guarantee you to build a software with [[one and only one type]] ...(start at 1296)= | ||
Create a generic compatibility operator, that allows you to create other functions through composition. | |||
{{#ev:youtube|ZhuHCtR3xq8|||| | {{#ev:youtube|ZhuHCtR3xq8|||| | ||
|start=1126&end=1230}} | |start=1126&end=1230}} |
Revision as of 07:20, 27 July 2021
Universality:You can convert any function into a table lookup... , and the function is just data (start at 355)
{{#ev:youtube|ZhuHCtR3xq8|||| |start=355&end=365}}
Monad in terms of Functions, Monoids, Monads...(starting at 455)
{{#ev:youtube|ZhuHCtR3xq8|||| |start=472&end=500}}
Monoid is the way to build complexity from simplicity...(start at 1010)
Simple in Brian's terms means small. I assume this means a smaller vocabulary, in the monoidal case, only one type, so in the size of type vocabulary, it is small. {{#ev:youtube|ZhuHCtR3xq8|||| |start=1010&end=1080}}
Monoid helps to guarantee you to build a software with one and only one type ...(start at 1296)
Create a generic compatibility operator, that allows you to create other functions through composition. {{#ev:youtube|ZhuHCtR3xq8|||| |start=1126&end=1230}}