Immutability On Thursday, August 11, 2016 at 2:37:33 PM UTC+5:30, Peter Damoc wrote: > > "The fundamental fact about learning: Anything is easy if you can > assimilate it to your collection of models. If you can't, anything can be > painfully difficult.” - Seymour Papert > > I'm trying to come up with a sorted list of concepts and models that a > prospective Elm user needs to learn in order become proficient in Elm. > > Here is my list (I actively tried to keep it short) : > > - types : the concept that information flowing through an Elm program has > a specific type and that the compiler will not accept the wrong type. > > - type composition: the concept that types can be composed into more > advanced types using union type syntax and record syntax. > > - type variables : the concept that you can have a type constructor that > can take arguments and produce a custom type (List, Maybe, etc) > > - functions as types: the concept that you can give functions to other > functions in order to customize their application. > > - currying/closures: the concept that you can take a multi argument > function and produce another function that has some of those arguments > applied. > > - declarative: the concept that the Elm programs are made of one big > function that returns a specific type instead of a series of instructions. > > How does your list looks like? Which one gave you most troubles? Which one > did you find most amazing | useful | mind-blowing ? > > > > > > -- > There is NO FATE, we are the creators. > blog: http://damoc.ro/ >
-- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
