<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Generics on BradCypert.com</title>
    <link>https://www.bradcypert.com/tags/generics/</link>
    <description>Recent content in Generics on BradCypert.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 27 Dec 2022 22:25:45 -0500</lastBuildDate>
    <atom:link href="https://www.bradcypert.com/tags/generics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Generics in Scala</title>
      <link>https://www.bradcypert.com/using-generics-in-scala/</link>
      <pubDate>Thu, 15 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://www.bradcypert.com/using-generics-in-scala/</guid>
      <description>&lt;p&gt;Scala has, in it’s core library, several classes that are intended to contain (at some point or another) some object. A few examples of this are seen in &lt;a href=&#34;https://www.scala-lang.org/api/2.12.2/scala/Option.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Option&lt;/a&gt;&#xA; and &lt;a href=&#34;https://www.scala-lang.org/api/2.12.2/scala/concurrent/Future.html&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Future&lt;/a&gt;&#xA;. These container classes allow you to act upon values that may or may not exist or even to work with values that should appear in the future (hence the name “Future”). The idea of these container classes is fundamentally simple. Let’s define a container class to hold an instance of class called Egg.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
