Difference between revisions of "Faking closures on the JVM isn't as simple as it looks"
From JVMLangSummit
Jump to navigationJump to searchLine 1: | Line 1: | ||
;Speaker: David Pollak | ;Speaker: David Pollak | ||
;Project: http://liftweb.net/ | ;Project: http://liftweb.net/ | ||
− | ;Resources: [http://medianetwork.oracle.com/media/show/15490 | + | ;Resources: [http://medianetwork.oracle.com/media/show/15490 Video] |
===Abstract=== | ===Abstract=== | ||
Scala is a hybrid function/OO language that fully supports and extends Java's object model as well as providing functions that close over current scope. Well, golly gosh, it seems easy at first, but when you dig down, stuff like non-final variables, lazy values and other constructs make closures non-trivial. David Pollak will explore Scala's functions and byte-code that allows the functions to close over current scope. | Scala is a hybrid function/OO language that fully supports and extends Java's object model as well as providing functions that close over current scope. Well, golly gosh, it seems easy at first, but when you dig down, stuff like non-final variables, lazy values and other constructs make closures non-trivial. David Pollak will explore Scala's functions and byte-code that allows the functions to close over current scope. |
Latest revision as of 12:21, 3 September 2010
- Speaker
- David Pollak
- Project
- http://liftweb.net/
- Resources
- Video
Abstract
Scala is a hybrid function/OO language that fully supports and extends Java's object model as well as providing functions that close over current scope. Well, golly gosh, it seems easy at first, but when you dig down, stuff like non-final variables, lazy values and other constructs make closures non-trivial. David Pollak will explore Scala's functions and byte-code that allows the functions to close over current scope.