<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Pi Ke</title>
    <description>The latest articles on DEV Community by Pi Ke (@pike0000).</description>
    <link>https://dev.to/pike0000</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F90651%2Fd9c16f2e-a104-4c3a-8b5c-136b308ae0b7.jpeg</url>
      <title>DEV Community: Pi Ke</title>
      <link>https://dev.to/pike0000</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pike0000"/>
    <language>en</language>
    <item>
      <title>How to Understand and Use nil in Golang Correctly?</title>
      <dc:creator>Pi Ke</dc:creator>
      <pubDate>Sat, 06 Jan 2024 14:05:16 +0000</pubDate>
      <link>https://dev.to/pike0000/how-to-understand-and-use-nil-in-golang-correctly-45pi</link>
      <guid>https://dev.to/pike0000/how-to-understand-and-use-nil-in-golang-correctly-45pi</guid>
      <description>&lt;p&gt;In Golang, nil is a predefined identifier that carries different meanings in various contexts, but typically represents "none", "empty" or "zero value". It can be assigned to variables of pointer, slice, map, channel, function, and interface types. Understanding the significance of nil is crucial for writing robust Go programs, as mishandling nil can lead to unexpected issues. nil in Pointers In G&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
