<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket v2 on 100 Exercises to Learn Go</title><link>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/</link><description>Recent content in Ticket v2 on 100 Exercises to Learn Go</description><generator>Hugo</generator><language>en</language><atom:link href="https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/index.xml" rel="self" type="application/rss+xml"/><item><title>Status</title><link>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/status/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/status/</guid><description>&lt;h1 id="status"&gt;Status&lt;a class="anchor" href="#status"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Tickets need a state: open, in progress, closed. Many languages hand you an
enum — a type with exactly three inhabitants and no others. Go doesn&amp;rsquo;t have
one. What it has is sneakier: an &lt;code&gt;int&lt;/code&gt; wearing a nametag, plus the
discipline to treat it like an enum anyway.&lt;/p&gt;
&lt;h2 id="an-int-in-a-costume"&gt;An int in a costume&lt;a class="anchor" href="#an-int-in-a-costume"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-go" data-lang="go"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#75715e"&gt;// Syntax: named type over int, constants counted by iota&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;type&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;Status&lt;/span&gt; &lt;span style="color:#66d9ef"&gt;int&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;const&lt;/span&gt; (
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#a6e22e"&gt;StatusOpen&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;Status&lt;/span&gt; = &lt;span style="color:#66d9ef"&gt;iota&lt;/span&gt; &lt;span style="color:#75715e"&gt;// 0&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#a6e22e"&gt;StatusInProgress&lt;/span&gt; &lt;span style="color:#75715e"&gt;// 1&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#a6e22e"&gt;StatusClosed&lt;/span&gt; &lt;span style="color:#75715e"&gt;// 2&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;code&gt;Status&lt;/code&gt; is a distinct type — you can&amp;rsquo;t pass a bare &lt;code&gt;int&lt;/code&gt; where a &lt;code&gt;Status&lt;/code&gt;
is expected without converting. But the costume is thin: &lt;code&gt;iota&lt;/code&gt; just counts
0, 1, 2 down the block (the bitwise lesson showed its other face), and
&lt;em&gt;any&lt;/em&gt; int converts back in. &lt;code&gt;Status(99)&lt;/code&gt; compiles. It means nothing, and
the compiler won&amp;rsquo;t stop it.&lt;/p&gt;</description></item><item><title>Ticket Errors</title><link>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/errors/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/errors/</guid><description>&lt;h1 id="ticket-errors"&gt;Ticket Errors&lt;a class="anchor" href="#ticket-errors"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Validation errors so far were one-off strings, created where needed and
compared nowhere. That stops working the moment a caller must &lt;em&gt;react&lt;/em&gt;
differently to different failures — retry on one, abort on another. This
exercise gives failures identities callers can test for, without losing the
human-readable story.&lt;/p&gt;
&lt;h2 id="name-the-failure"&gt;Name the failure&lt;a class="anchor" href="#name-the-failure"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-go" data-lang="go"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;var&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;ErrUnknownStatus&lt;/span&gt; = &lt;span style="color:#a6e22e"&gt;errors&lt;/span&gt;.&lt;span style="color:#a6e22e"&gt;New&lt;/span&gt;(&lt;span style="color:#e6db74"&gt;&amp;#34;unknown status&amp;#34;&lt;/span&gt;)&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;A &lt;strong&gt;sentinel error&lt;/strong&gt; is a package-level variable naming one specific thing
that can go wrong. Capital E, &lt;code&gt;Err&lt;/code&gt; prefix, created once with
&lt;code&gt;errors.New&lt;/code&gt; — the convention is rigid because its power is social: every
caller recognizes the name. Comparing with &lt;code&gt;==&lt;/code&gt; works when the exact value
travels untouched, but messages get wrapped along the way (next section),
so the robust test unwraps:&lt;/p&gt;</description></item><item><title>Wrap</title><link>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/wrap/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/wrap/</guid><description>&lt;h1 id="wrap"&gt;Wrap&lt;a class="anchor" href="#wrap"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The previous exercise wrapped a sentinel at construction time. This one
wraps on the &lt;em&gt;lookup&lt;/em&gt; path — searching a list, missing, and reporting the
miss so precisely that callers can distinguish &amp;ldquo;not found&amp;rdquo; from every other
failure. Same verbs, new territory: the verb choice is the lesson.&lt;/p&gt;
&lt;h2 id="the-search-that-can-miss"&gt;The search that can miss&lt;a class="anchor" href="#the-search-that-can-miss"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-go" data-lang="go"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;func&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;FindTicket&lt;/span&gt;(&lt;span style="color:#a6e22e"&gt;ids&lt;/span&gt; []&lt;span style="color:#66d9ef"&gt;int&lt;/span&gt;, &lt;span style="color:#a6e22e"&gt;id&lt;/span&gt; &lt;span style="color:#66d9ef"&gt;int&lt;/span&gt;) (&lt;span style="color:#66d9ef"&gt;int&lt;/span&gt;, &lt;span style="color:#66d9ef"&gt;error&lt;/span&gt;) {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;for&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;i&lt;/span&gt;, &lt;span style="color:#a6e22e"&gt;v&lt;/span&gt; &lt;span style="color:#f92672"&gt;:=&lt;/span&gt; &lt;span style="color:#66d9ef"&gt;range&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;ids&lt;/span&gt; {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;if&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;v&lt;/span&gt; &lt;span style="color:#f92672"&gt;==&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;id&lt;/span&gt; {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;return&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;i&lt;/span&gt;, &lt;span style="color:#66d9ef"&gt;nil&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; }
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; }
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;return&lt;/span&gt; &lt;span style="color:#f92672"&gt;-&lt;/span&gt;&lt;span style="color:#ae81ff"&gt;1&lt;/span&gt;, &lt;span style="color:#a6e22e"&gt;fmt&lt;/span&gt;.&lt;span style="color:#a6e22e"&gt;Errorf&lt;/span&gt;(&lt;span style="color:#e6db74"&gt;&amp;#34;ticket %d: %w&amp;#34;&lt;/span&gt;, &lt;span style="color:#a6e22e"&gt;id&lt;/span&gt;, &lt;span style="color:#a6e22e"&gt;ErrNotFound&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Two conventions share this small function. The index pair &lt;code&gt;(-1, err)&lt;/code&gt;:
&lt;code&gt;-1&lt;/code&gt; is never a valid index, so it unambiguously means &amp;ldquo;no position,&amp;rdquo; while
the error carries &lt;em&gt;why&lt;/em&gt;. And the loop itself — &lt;code&gt;for i, v := range ids&lt;/code&gt;,
both variables this time, because position is the product being sold.&lt;/p&gt;</description></item><item><title>Join</title><link>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/join/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/join/</guid><description>&lt;h1 id="join"&gt;Join&lt;a class="anchor" href="#join"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Every validator so far stopped at the first complaint. One bad title &lt;em&gt;or&lt;/em&gt;
one short description — never both, even when both are wrong. That&amp;rsquo;s
fail-fast, and it&amp;rsquo;s rude: the user fixes the title, resubmits, and only
then learns about the description. Forms, configs, and APIs all deserve
better: the full list, in one round trip.&lt;/p&gt;
&lt;h2 id="collect-then-combine"&gt;Collect, then combine&lt;a class="anchor" href="#collect-then-combine"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-go" data-lang="go"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;var&lt;/span&gt; (
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#a6e22e"&gt;ErrBadTitle&lt;/span&gt; = &lt;span style="color:#a6e22e"&gt;errors&lt;/span&gt;.&lt;span style="color:#a6e22e"&gt;New&lt;/span&gt;(&lt;span style="color:#e6db74"&gt;&amp;#34;bad title&amp;#34;&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#a6e22e"&gt;ErrBadDesc&lt;/span&gt; = &lt;span style="color:#a6e22e"&gt;errors&lt;/span&gt;.&lt;span style="color:#a6e22e"&gt;New&lt;/span&gt;(&lt;span style="color:#e6db74"&gt;&amp;#34;bad description&amp;#34;&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;func&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;ValidateAll&lt;/span&gt;(&lt;span style="color:#a6e22e"&gt;title&lt;/span&gt;, &lt;span style="color:#a6e22e"&gt;desc&lt;/span&gt; &lt;span style="color:#66d9ef"&gt;string&lt;/span&gt;) &lt;span style="color:#66d9ef"&gt;error&lt;/span&gt; {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;var&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;errs&lt;/span&gt; []&lt;span style="color:#66d9ef"&gt;error&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;if&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;title&lt;/span&gt; &lt;span style="color:#f92672"&gt;==&lt;/span&gt; &lt;span style="color:#e6db74"&gt;&amp;#34;&amp;#34;&lt;/span&gt; {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#a6e22e"&gt;errs&lt;/span&gt; = append(&lt;span style="color:#a6e22e"&gt;errs&lt;/span&gt;, &lt;span style="color:#a6e22e"&gt;ErrBadTitle&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; }
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;if&lt;/span&gt; len(&lt;span style="color:#a6e22e"&gt;desc&lt;/span&gt;) &amp;lt; &lt;span style="color:#ae81ff"&gt;10&lt;/span&gt; {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#a6e22e"&gt;errs&lt;/span&gt; = append(&lt;span style="color:#a6e22e"&gt;errs&lt;/span&gt;, &lt;span style="color:#a6e22e"&gt;ErrBadDesc&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; }
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;return&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;errors&lt;/span&gt;.&lt;span style="color:#a6e22e"&gt;Join&lt;/span&gt;(&lt;span style="color:#a6e22e"&gt;errs&lt;/span&gt;&lt;span style="color:#f92672"&gt;...&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Each rule appends its sentinel independently — no &lt;code&gt;else&lt;/code&gt;, no early return,
no rule aware of the others. Then &lt;code&gt;errors.Join&lt;/code&gt; fuses the collection into
one error. The fusion preserves every identity: &lt;code&gt;errors.Is(joined, ErrBadTitle)&lt;/code&gt; and &lt;code&gt;errors.Is(joined, ErrBadDesc)&lt;/code&gt; both hold, so callers
test parts exactly as if each had arrived alone.&lt;/p&gt;</description></item><item><title>Panic vs Error</title><link>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/panic_vs_error/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/panic_vs_error/</guid><description>&lt;h1 id="panic-vs-error"&gt;Panic vs Error&lt;a class="anchor" href="#panic-vs-error"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The panics lesson drew the line: panic for bugs, return errors for
conditions. This exercise lives exactly on that line — a function that
&lt;em&gt;receives&lt;/em&gt; a panic from below and hands an &lt;em&gt;error-shaped answer&lt;/em&gt; upward,
so its own callers never know an explosion happened inside.&lt;/p&gt;
&lt;h2 id="the-boundary-pattern"&gt;The boundary pattern&lt;a class="anchor" href="#the-boundary-pattern"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-go" data-lang="go"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;func&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;parseOrPanic&lt;/span&gt;(&lt;span style="color:#a6e22e"&gt;s&lt;/span&gt; &lt;span style="color:#66d9ef"&gt;string&lt;/span&gt;) &lt;span style="color:#66d9ef"&gt;int&lt;/span&gt; {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;if&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;s&lt;/span&gt; &lt;span style="color:#f92672"&gt;==&lt;/span&gt; &lt;span style="color:#e6db74"&gt;&amp;#34;&amp;#34;&lt;/span&gt; {
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; panic(&lt;span style="color:#e6db74"&gt;&amp;#34;empty input&amp;#34;&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; }
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; &lt;span style="color:#66d9ef"&gt;return&lt;/span&gt; len(&lt;span style="color:#a6e22e"&gt;s&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;}&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;code&gt;parseOrPanic&lt;/code&gt; panics on empty input — by its own contract, callers must
not pass &lt;code&gt;&amp;quot;&amp;quot;&lt;/code&gt;. But &lt;code&gt;MustParse&lt;/code&gt; promises something friendlier: the length,
or &lt;code&gt;-1&lt;/code&gt; for empty, with &lt;em&gt;no panic escaping&lt;/em&gt;. Somebody has to stand between
those two contracts and translate. That somebody is &lt;code&gt;defer&lt;/code&gt; plus &lt;code&gt;recover&lt;/code&gt;:&lt;/p&gt;</description></item><item><title>Custom Errors and errors.As</title><link>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/errors_as/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://hamzahraihan.github.io/100-exercises-to-learn-go/05_ticket_v2/errors_as/</guid><description>&lt;h1 id="custom-errors-and-errorsas"&gt;Custom Errors and errors.As&lt;a class="anchor" href="#custom-errors-and-errorsas"&gt;&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;&lt;code&gt;errors.Is&lt;/code&gt; matches identity — is this error &lt;em&gt;that&lt;/em&gt; sentinel? &lt;code&gt;errors.As&lt;/code&gt; matches structure — is this error (or anything it wraps) &lt;em&gt;of this type&lt;/em&gt;? The difference matters when you need data out of the error, not just a yes/no.&lt;/p&gt;
&lt;h2 id="the-limit-of-sentinels"&gt;The limit of sentinels&lt;a class="anchor" href="#the-limit-of-sentinels"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-go" data-lang="go"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;var&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;ErrNotFound&lt;/span&gt; = &lt;span style="color:#a6e22e"&gt;errors&lt;/span&gt;.&lt;span style="color:#a6e22e"&gt;New&lt;/span&gt;(&lt;span style="color:#e6db74"&gt;&amp;#34;not found&amp;#34;&lt;/span&gt;)
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#75715e"&gt;// caller knows it&amp;#39;s not found, but which ID?&lt;/span&gt;
&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#66d9ef"&gt;return&lt;/span&gt; &lt;span style="color:#a6e22e"&gt;ErrNotFound&lt;/span&gt; &lt;span style="color:#75715e"&gt;// data lost&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Sentinels are identity tags. They carry no payload. When the error needs context — which field failed, what value was rejected, which ID was missing — a sentinel is the wrong tool.&lt;/p&gt;</description></item></channel></rss>