By cjsmith
via morepypy.blogspot.com
Published: Feb 02 2012 / 08:09
This is the second blog post in a series about comparing partial evaluation and tracing. In the first post of the series I introduced a small flow-graph language together with an interpreter for it. Then I showed a partial evaluator for the language. In this post I will show how a tracer for the same language works and how it relates to both execution and to partial evaluation.
-
Compiling to CPS in Javascript: stepping debuggers, no callback hell, and more
-
Things worth learning in Scrum Master Certification
-
Why Method Overloading Sucks in Scala
-
Progressive F# Tutorials June 5-6th 2012 NYC
-
Why I created cull.io - A new tool to pre-qualify candidates for an interview
-
Introducing Apache Hive Query Patterns
Add your comment
