translated part 1.2 'Types and Functions'

[s-km]

I tried to follow similar conventions as in category-the-essence-of-composition.md, but there are a bunch of different ways to translate the Haskell code snippets to Scala, so it'd be nice if we could make a short style guide or something to keep things consistent

ex 1 val fact = (n: Int) => (1 to n toList) product vs. val fact = (n: Int) => (1 to n).toList.product vs. val fact = (n: Int) => List.range(1, n).product vs. def fact(n: Int) = (1 to n).toList.product etc.

ex 2

fInt :: Integer -> ()
fInt x = ()

val fInt: BigInt => Unit = x => ()

................

fInt :: Integer -> ()
fInt _ = ()

val fInt: BigInt => Unit = _ => ()

vs

fInt :: Integer -> ()
fInt x = ()

fInt _ = ()

val fInt: BigInt => Unit = x => ()

val fInt: BigInt => Unit = _ => ()

[SystemFw]

I'd personally prefer to avoid postfix ops, so (1 to n).toList.product

[kailuowang]

Shall we use "tut:silent" instead of "scala", for all the compilable code?

[s-km]

@kailuowang The only 'problem' I see with that is that you'd get inconsistent syntax highlighting with how we're currently doing things. Though, it'd be simple enough to just change tut target and source directory settings, and have something like this:

CT_from_Programmers.scala/
  ├── project/
  │   └── build.properties
  │   └── plugins.sbt
  ├── src/
  │   └── main/
  │       └── tut/
  │           └── file_with_tut:silent_tags1.md
  │           └── file_with_tut:silent_tags2.md
  │           └── file_with_tut:silent_tags3.md
  └── translations/
  │   └── tut_output_file_with_scala_tags1.md
  │   └── tut_output_file_with_scala_tags2.md
  │   └── tut_output_ile_with_scala_tags3.md
  └── .gitignore
  └── .travis.yml
  └── README.md
  └── build.sbt

[kailuowang]

I wouldn't worry about the syntax highlighting in this repo. My plan is that after we finish we just going to use tut to compile the main/src/tut/*.md files and handover Bartosz the target md files or HTML files from Jekyll on top of that. After he manually edit in our sample code in his posts, it might loss syntax highlighting like the current haskell and c++ code.