<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Static on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/static/</link>
    <description>Recent content in Static on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Nov 2022 15:36:37 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/static/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Static Methods, Companion Objects, and Testing</title>
      <link>https://www.bradcypert.com/static-methods-companion-objects-and-testing/</link>
      <pubDate>Wed, 18 Jul 2018 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/static-methods-companion-objects-and-testing/</guid>
      <description>&lt;p&gt;I’ve been working with Kotlin a ton recently, both at work and for fun. It’s a fantastic language on the JVM that combines almost all of my favorite Scala features and adds in several new features as well. If you haven’t given it a shot yet and you’re a Java reader, give it a try! You’ll love how expressive it can be and how simple and concise some of the code can be. If you’re a Scala reader, you’ll feel familiar with a lot of the syntax and ideas (Objects, replacing statics for example). One thing Kotlin does that still feels a bit weird is it promotes the use of companion objects. A companion object sits inside a class definition and houses all the &lt;code&gt;static&lt;/code&gt; methods which that class will own. Let’s convert a piece of Java code to Kotlin so you can see what I mean.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
