<?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>Type Inference on TheJavaGuy Blog 🚀</title>
    <link>/tags/type-inference/</link>
    <description>Recent content in Type Inference on TheJavaGuy Blog 🚀</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © 2016-2026 Ivan Milosavljević. All Rights Reserved.
</copyright>
    <lastBuildDate>Thu, 08 Dec 2022 00:00:00 +0000</lastBuildDate><atom:link href="/tags/type-inference/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>3 ways to write higher quality software by using type inference</title>
      <link>/posts/017-3-ways-to-write-higher-quality-software-by-using-type-inference/</link>
      <pubDate>Thu, 08 Dec 2022 00:00:00 +0000</pubDate>
      <guid>/posts/017-3-ways-to-write-higher-quality-software-by-using-type-inference/</guid>
      <description><![CDATA[<p>When hearing the words &ldquo;type inference&rdquo;, most developers probably think of local-variable type inference that arrived in Java 10. But type inference in Java is much older than that. Some sort of it existed even in Java 6, where compilers could infer type parameters of generic constructors! For sure the most famous type inference example is the diamond operator in Java 7. Since the beginning, mere reduction of number of characters used in source code went hand in hand with type inference. But is that its biggest advantage?</p>]]></description><enclosure url="/posts/017-3-ways-to-write-higher-quality-software-by-using-type-inference/cover.png" length="77839" type="image/png" />
    </item>
    
  </channel>
</rss>

