Difference between revisions of "Pronunciation"

From HaskellWiki
Jump to navigation Jump to search
(wording correction.)
m (Remove trailing whitespace in <hask> tags)
(20 intermediate revisions by 8 users not shown)
Line 1: Line 1:
  +
There was a thread on Haskell-Cafe about [http://www.haskell.org/pipermail/haskell-cafe/2008-January/038756.html how to pronounce Haskell].
Some notes for beginners on how to pronounce those strange Haskell operators etc.
 
   
  +
Below are some notes for beginners on how to pronounce those strange Haskell operators and 'read' Haskell programs.
This is just a rough start to this page. Obviously needs more work.
 
   
This can be a table with formal and informal ways of saying various operators and code snippets such as
+
This is meant to be a table with formal and informal ways of saying various operators and code snippets.
   
  +
{|
<hask> -> </hask> maps to, to
 
  +
! Symbol
  +
! Pronunciation
  +
! References
  +
|-
  +
| <hask>::</hask>
  +
| has type (in definitions); at type (in expressions or patterns)
  +
|-
  +
| <hask>-></hask>
  +
| maps to, to
  +
|-
  +
| <hask>=</hask>
  +
| is
  +
|-
  +
| <hask>==</hask>
  +
| equals
  +
| [http://haskell.org/ghc/docs/latest/html/libraries/base/Prelude.html#v%3A-61--61- Prelude]
  +
|-
  +
| <hask>/=</hask>
  +
| not equals
  +
| [http://haskell.org/ghc/docs/latest/html/libraries/base/Prelude.html#v%3A-61--61- Prelude]
  +
|-
  +
| <hask>=></hask>
  +
| is a witness for, implies
  +
| [http://www.haskell.org/tutorial/classes.html Type Classes and Overloading]
  +
|-
  +
| <hask>.</hask>
  +
| dot (could be used anywhere, but especially in, for example, Data.Char.ord), ring, compose (for example, negate . (+1)), (silent) (for example, forall a. (Num a) => a)
  +
|-
  +
| <hask><-</hask>
  +
| drawn from, from
  +
|-
  +
| <hask>-<</hask>
  +
| arrow application
  +
| [http://haskell.org/arrows/syntax.html Arrows syntax]
  +
|-
  +
| <hask>&&&</hask>
  +
| both, fanout
  +
| [http://www.haskell.org/ghc/docs/latest/html/libraries/base/Control-Arrow.html Control.Arrow]
  +
|-
  +
| <hask>|||</hask>
  +
| either, fanin
  +
| [http://www.haskell.org/ghc/docs/latest/html/libraries/base/Control-Arrow.html#v%3A%7C%7C%7C Control.Arrow]
  +
|
  +
|-
  +
| <hask>++</hask>
  +
| append
  +
| [http://haskell.org/ghc/docs/latest/html/libraries/base/Prelude.html#v%3A-43--43- Prelude]
  +
|-
  +
| <hask>>>=</hask>
  +
| bind
  +
| [http://www.haskell.org/tutorial/monads.html About monads]
  +
[[Monads as containers]]
  +
|-
  +
| <hask>>></hask>
  +
| then, sequence
  +
| [http://haskell.org/ghc/docs/latest/html/libraries/base/Prelude.html#v:-62--62- Prelude]
  +
|-
  +
| <hask><*></hask>
  +
| applied over
  +
| [http://www.haskell.org/haskellwiki/Applicative_functor Applicative Functors]
  +
|-
  +
| <hask>\</hask>
  +
| lambda
  +
| [[Lambda abstraction]]
  +
[http://www.haskell.org/onlinereport/exps.html#sect3.3 Haskell 98 Report]
  +
|-
  +
| <hask>!</hask>
  +
| bang; strict (in patterns or data definitions); index (in expressions)
  +
| [http://www.haskell.org/ghc/docs/latest/html/users_guide/bang-patterns.html Bang Patterns]
  +
[[Keywords]]
  +
|-
  +
| <hask>~</hask>
  +
| irrefutable, lazy (in patterns)
  +
|-
  +
| <hask>:</hask>
  +
| cons
  +
|-
  +
| <hask>[]</hask>
  +
| nil
  +
|-
  +
| <hask>()</hask>
  +
| unit
  +
|-
  +
| <hask>(,)</hask>
  +
| 2-tuple, pair
  +
|-
  +
| <hask>(a,b,c)</hask>
  +
| [3-]tuple [of] a, b, and c
  +
|-
  +
| <hask>({)}</hask>
  +
| just as inconvenient to convey grouping verbally, whether it's layout or punctuation
  +
|}
   
  +
{|
<hask> -< </hask>
 
  +
! Example
  +
! Pronunciation
  +
|-
  +
| <hask>f :: Int -> Int</hask>
  +
| f has type Int to Int
  +
|}
   
  +
Thoughts on improving this page:
<hask> => </hask> is a witness for, implies
 
 
<hask> . </hask> ring, dot
 
 
<hask> <- </hask> drawn from, from
 
 
<hask> ++ </hask> append
 
 
<hask> +++ </hask>
 
 
<hask> >>= </hask> bind
 
 
<hask>f :: Int -> Int</hask> f has type Int to Int
 
   
  +
The tables above would be best split into more columns to distinguish Informal, possibly bad suggestions like "then", "is", "gets", from Formal correct ways of saying the same thing. The Symbols could also be named in a literal way in another column, such as "arrow" or "double-colon". The Description column can be quite brief and a link provided to the relevant wiki page for the operator.
   
  +
Some words, particularly the informal ones, may be good for several different symbols, but these can hopefully be arranged so that their context will make them unambiguous when reading a code snippet.
   
 
[[Category:Syntax]]
 
[[Category:Syntax]]

Revision as of 23:21, 17 December 2013

There was a thread on Haskell-Cafe about how to pronounce Haskell.

Below are some notes for beginners on how to pronounce those strange Haskell operators and 'read' Haskell programs.

This is meant to be a table with formal and informal ways of saying various operators and code snippets.

Symbol Pronunciation References
:: has type (in definitions); at type (in expressions or patterns)
-> maps to, to
= is
== equals Prelude
/= not equals Prelude
=> is a witness for, implies Type Classes and Overloading
. dot (could be used anywhere, but especially in, for example, Data.Char.ord), ring, compose (for example, negate . (+1)), (silent) (for example, forall a. (Num a) => a)
<- drawn from, from
-< arrow application Arrows syntax
&&& both, fanout Control.Arrow
||| either, fanin Control.Arrow
++ append Prelude
>>= bind About monads
Monads as containers
>> then, sequence Prelude
<*> applied over Applicative Functors
\ lambda Lambda abstraction
Haskell 98 Report
! bang; strict (in patterns or data definitions); index (in expressions) Bang Patterns
Keywords
~ irrefutable, lazy (in patterns)
: cons
[] nil
() unit
(,) 2-tuple, pair
(a,b,c) [3-]tuple [of] a, b, and c
({)} just as inconvenient to convey grouping verbally, whether it's layout or punctuation
Example Pronunciation
f :: Int -> Int f has type Int to Int

Thoughts on improving this page:

The tables above would be best split into more columns to distinguish Informal, possibly bad suggestions like "then", "is", "gets", from Formal correct ways of saying the same thing. The Symbols could also be named in a literal way in another column, such as "arrow" or "double-colon". The Description column can be quite brief and a link provided to the relevant wiki page for the operator.

Some words, particularly the informal ones, may be good for several different symbols, but these can hopefully be arranged so that their context will make them unambiguous when reading a code snippet.