<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Boxing on Bits, Trades &amp; Systems</title>
    <link>https://blog.turboawesome.win/tags/boxing/</link>
    <description>Recent content in Boxing on Bits, Trades &amp; Systems</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 08 Jan 2014 09:44:00 +0000</lastBuildDate>
    <atom:link href="https://blog.turboawesome.win/tags/boxing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Scala on the Hot Path: Where the Abstraction Cost Goes</title>
      <link>https://blog.turboawesome.win/2014/01/scala-on-the-hot-path-where-the-abstraction-cost-goes/</link>
      <pubDate>Wed, 08 Jan 2014 09:44:00 +0000</pubDate>
      <guid>https://blog.turboawesome.win/2014/01/scala-on-the-hot-path-where-the-abstraction-cost-goes/</guid>
      <description>Scala&amp;#39;s abstractions are elegant — but on the JVM, elegance has a bytecode cost. Understanding where Scala generates boxing, closures, and virtual dispatch tells you which patterns are safe in hot paths and which aren&amp;#39;t.</description>
    </item>
  </channel>
</rss>
