https://wiki.jvmlangsummit.com/api.php?action=feedcontributions&feedformat=atom&user=Siek 2026-05-23T05:58:19Z User contributions MediaWiki 1.32.0 https://wiki.jvmlangsummit.com/index.php?title=File:Jvm-summit-2009.pdf&diff=375 2009-09-18T21:20:04Z

<p>Siek: uploaded a new version of &quot;Image:Jvm-summit-2009.pdf&quot;: Slides for the talk &quot;Blame Tracking&quot; at the JVM Languages Summit 2009.</p> <hr /> <div>Slides for the talk &quot;Blame Tracking&quot; at the JVM Languages Summit 2009.</div>

Siek https://wiki.jvmlangsummit.com/index.php?title=Blame_Tracking&diff=364 2009-09-18T16:03:45Z

<p>Siek: /* Blame Tracking */</p> <hr /> <div>== Blame Tracking ==<br /> Jeremy Siek, http://ecee.colorado.edu/~siek<br /> <br /> ; Project: <br /> ; Blog: <br /> ; Slides: [[Media:Jvm-summit-2009.pdf]]<br /> <br /> === Abstract ===<br /> <br /> Blame Tracking for Gradual Types — Jeremy Siek<br /> <br /> Have you ever called a library function in a dynamic language only to have an exception thrown from deep inside the function? Is the error your fault (good heavens no!) or the fault of of the library writer? With the addition of gradual typing, it becomes possible to address this problem using a technology called blame tracking. The idea behind blame tracking is to enclose objects in a wrapper that represents the type that the object is suppose to have and that includes source information (line number, etc.) for where the object was cast to that type. If the object ever disobeys it's type, or is misused as if it had a different type, then the run-time system flags an error and tells the programmer who is to blame. In this presentation I will give an in-depth description of blame tracking and discuss recent research on how to reduce the run-time overhead of blame tracking to a constant factor.<br /> <br /> = Background =<br /> <br /> <br /> = Current Status =<br /> <br /> <br /> = Future =<br /> <br /> <br /> = Key Issues for Discussion =<br /> ''(please expand cooperatively)''</div>

Siek https://wiki.jvmlangsummit.com/index.php?title=Blame_Tracking&diff=363 2009-09-18T16:03:31Z

<p>Siek: /* Blame Tracking */</p> <hr /> <div>== Blame Tracking ==<br /> Jeremy Siek, http://ecee.colorado.edu/~siek<br /> <br /> ; Project: <br /> ; Blog: <br /> ; Slides: [[Jvm-summit-2009.pdf]]<br /> <br /> === Abstract ===<br /> <br /> Blame Tracking for Gradual Types — Jeremy Siek<br /> <br /> Have you ever called a library function in a dynamic language only to have an exception thrown from deep inside the function? Is the error your fault (good heavens no!) or the fault of of the library writer? With the addition of gradual typing, it becomes possible to address this problem using a technology called blame tracking. The idea behind blame tracking is to enclose objects in a wrapper that represents the type that the object is suppose to have and that includes source information (line number, etc.) for where the object was cast to that type. If the object ever disobeys it's type, or is misused as if it had a different type, then the run-time system flags an error and tells the programmer who is to blame. In this presentation I will give an in-depth description of blame tracking and discuss recent research on how to reduce the run-time overhead of blame tracking to a constant factor.<br /> <br /> = Background =<br /> <br /> <br /> = Current Status =<br /> <br /> <br /> = Future =<br /> <br /> <br /> = Key Issues for Discussion =<br /> ''(please expand cooperatively)''</div>

Siek https://wiki.jvmlangsummit.com/index.php?title=Blame_Tracking&diff=362 2009-09-18T16:03:11Z

<p>Siek: /* Blame Tracking */</p> <hr /> <div>== Blame Tracking ==<br /> Jeremy Siek, http://ecee.colorado.edu/~siek<br /> <br /> ; Project: <br /> ; Blog: <br /> ; Slides: [[Media:Jvm-summit-2009.pdf]]<br /> <br /> === Abstract ===<br /> <br /> Blame Tracking for Gradual Types — Jeremy Siek<br /> <br /> Have you ever called a library function in a dynamic language only to have an exception thrown from deep inside the function? Is the error your fault (good heavens no!) or the fault of of the library writer? With the addition of gradual typing, it becomes possible to address this problem using a technology called blame tracking. The idea behind blame tracking is to enclose objects in a wrapper that represents the type that the object is suppose to have and that includes source information (line number, etc.) for where the object was cast to that type. If the object ever disobeys it's type, or is misused as if it had a different type, then the run-time system flags an error and tells the programmer who is to blame. In this presentation I will give an in-depth description of blame tracking and discuss recent research on how to reduce the run-time overhead of blame tracking to a constant factor.<br /> <br /> = Background =<br /> <br /> <br /> = Current Status =<br /> <br /> <br /> = Future =<br /> <br /> <br /> = Key Issues for Discussion =<br /> ''(please expand cooperatively)''</div>

Siek https://wiki.jvmlangsummit.com/index.php?title=Blame_Tracking&diff=361 2009-09-18T16:02:30Z

<p>Siek: /* Blame Tracking */</p> <hr /> <div>== Blame Tracking ==<br /> Jeremy Siek, http://ecee.colorado.edu/~siek<br /> <br /> ; Project: <br /> ; Blog: <br /> ; Slides: [[Image:Jvm-summit-2009.pdf]]<br /> <br /> === Abstract ===<br /> <br /> Blame Tracking for Gradual Types — Jeremy Siek<br /> <br /> Have you ever called a library function in a dynamic language only to have an exception thrown from deep inside the function? Is the error your fault (good heavens no!) or the fault of of the library writer? With the addition of gradual typing, it becomes possible to address this problem using a technology called blame tracking. The idea behind blame tracking is to enclose objects in a wrapper that represents the type that the object is suppose to have and that includes source information (line number, etc.) for where the object was cast to that type. If the object ever disobeys it's type, or is misused as if it had a different type, then the run-time system flags an error and tells the programmer who is to blame. In this presentation I will give an in-depth description of blame tracking and discuss recent research on how to reduce the run-time overhead of blame tracking to a constant factor.<br /> <br /> = Background =<br /> <br /> <br /> = Current Status =<br /> <br /> <br /> = Future =<br /> <br /> <br /> = Key Issues for Discussion =<br /> ''(please expand cooperatively)''</div>

Siek https://wiki.jvmlangsummit.com/index.php?title=Blame_Tracking&diff=360 2009-09-18T16:02:19Z

<p>Siek: /* Blame Tracking */</p> <hr /> <div>== Blame Tracking ==<br /> Jeremy Siek, http://ecee.colorado.edu/~siek<br /> <br /> ; Project: <br /> ; Blog: <br /> ; Slides: [[Image:Jvm-summit-2009.pdf.pdf]]<br /> <br /> === Abstract ===<br /> <br /> Blame Tracking for Gradual Types — Jeremy Siek<br /> <br /> Have you ever called a library function in a dynamic language only to have an exception thrown from deep inside the function? Is the error your fault (good heavens no!) or the fault of of the library writer? With the addition of gradual typing, it becomes possible to address this problem using a technology called blame tracking. The idea behind blame tracking is to enclose objects in a wrapper that represents the type that the object is suppose to have and that includes source information (line number, etc.) for where the object was cast to that type. If the object ever disobeys it's type, or is misused as if it had a different type, then the run-time system flags an error and tells the programmer who is to blame. In this presentation I will give an in-depth description of blame tracking and discuss recent research on how to reduce the run-time overhead of blame tracking to a constant factor.<br /> <br /> = Background =<br /> <br /> <br /> = Current Status =<br /> <br /> <br /> = Future =<br /> <br /> <br /> = Key Issues for Discussion =<br /> ''(please expand cooperatively)''</div>

Siek https://wiki.jvmlangsummit.com/index.php?title=File:Jvm-summit-2009.pdf&diff=359 2009-09-18T16:01:11Z

<p>Siek: Slides for the talk &quot;Blame Tracking&quot; at the JVM Languages Summit 2009.</p> <hr /> <div>Slides for the talk &quot;Blame Tracking&quot; at the JVM Languages Summit 2009.</div>

Siek https://wiki.jvmlangsummit.com/index.php?title=Blame_Tracking&diff=321 2009-09-17T18:26:15Z

<p>Siek: /* Blame Tracking */</p> <hr /> <div>== Blame Tracking ==<br /> Jeremy Siek, http://ecee.colorado.edu/~siek<br /> <br /> ; Project: <br /> ; Blog: <br /> ; Slides: [[Image:file.pdf]]<br /> <br /> === Abstract ===<br /> <br /> Blame Tracking for Gradual Types — Jeremy Siek<br /> <br /> Have you ever called a library function in a dynamic language only to have an exception thrown from deep inside the function? Is the error your fault (good heavens no!) or the fault of of the library writer? With the addition of gradual typing, it becomes possible to address this problem using a technology called blame tracking. The idea behind blame tracking is to enclose objects in a wrapper that represents the type that the object is suppose to have and that includes source information (line number, etc.) for where the object was cast to that type. If the object ever disobeys it's type, or is misused as if it had a different type, then the run-time system flags an error and tells the programmer who is to blame. In this presentation I will give an in-depth description of blame tracking and discuss recent research on how to reduce the run-time overhead of blame tracking to a constant factor.<br /> <br /> = Background =<br /> <br /> <br /> = Current Status =<br /> <br /> <br /> = Future =<br /> <br /> <br /> = Key Issues for Discussion =<br /> ''(please expand cooperatively)''</div>

Siek