Martin Odersky

Martin Odersky’s Followers (34)

member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo
member photo

Martin Odersky



Average rating: 4.18 · 1,887 ratings · 117 reviews · 11 distinct worksSimilar authors
Programming in Scala: A Com...

by
4.22 avg rating — 1,663 ratings — published 2008 — 19 editions
Rate this book
Clear rating
Scala for the Impatient

by
4.09 avg rating — 638 ratings — published 2012 — 15 editions
Rate this book
Clear rating
Scala in Depth

by
3.87 avg rating — 193 ratings — published 2012 — 4 editions
Rate this book
Clear rating
Scala By Example

4.04 avg rating — 24 ratings — published 2014
Rate this book
Clear rating
ECOOP 2004 - Object-Oriente...

it was amazing 5.00 avg rating — 3 ratings — published 2004 — 4 editions
Rate this book
Clear rating
Programming in Scala by Mar...

it was amazing 5.00 avg rating — 1 rating2 editions
Rate this book
Clear rating
Compiler Construction: 16th...

it was amazing 5.00 avg rating — 1 rating — published 2007 — 3 editions
Rate this book
Clear rating
New Approach to Formal Lang...

0.00 avg rating — 0 ratings
Rate this book
Clear rating
[ECOOP 2004 - Object-Orient...

by
0.00 avg rating — 0 ratings
Rate this book
Clear rating
Abstract State Machines - T...

by
0.00 avg rating — 0 ratings — published 2000 — 3 editions
Rate this book
Clear rating
More books by Martin Odersky…
Quotes by Martin Odersky  (?)
Quotes are added by the Goodreads community and are not verified by Goodreads. (Learn more)

“In the absence of any explicit return statement, a Scala method returns the last value computed by the method.”
Martin Odersky, Programming in Scala Fifth Edition: Updated for Scala 3.0

“You may be wondering why you can't access the elements of a tuple like the elements of a list, for example, with "pair(0)". The reason is that a list's apply method always returns the same type, but each element of a tuple may be a different type: _1 can have one result type, _2 another, and so on.”
Martin Odersky, Programming in Scala

“The argument goes that since such type systems can only detect simple errors, whereas unit tests provide more extensive coverage, why bother with static types at all?”
Martin Odersky, Programming in Scala Fifth Edition: Updated for Scala 3.0

Topics Mentioning This Author

topics posts views last activity  
Java Programming: 2020 April/May Programming in Scala 1 3 Apr 03, 2020 07:29AM  


Is this you? Let us know. If not, help out and invite Martin to Goodreads.