<p dir="auto"></p><div class="Box Box--condensed my-2">
  <div class="Box-header f6">
    <p class="mb-0 text-bold">
      <a href="https://github.com/JuliaLang/julia/blob/54adf2193a6ea1b10cd1a184a7ba863aa985eede/stdlib/LinearAlgebra/src/matmul.jl#L536">julia/stdlib/LinearAlgebra/src/matmul.jl</a>
    </p>
    <p class="mb-0 color-fg-muted">
         Line 536
      in
      <a data-pjax="true" class="commit-tease-sha" href="/JuliaLang/julia/commit/54adf2193a6ea1b10cd1a184a7ba863aa985eede">54adf21</a>
    </p>
  </div>
  <div itemprop="text" class="Box-body p-0 blob-wrapper blob-wrapper-embedded data">
    <table class="highlight tab-size mb-0 js-file-line-container" data-tab-size="8" data-paste-markdown-skip="">

        <tbody><tr class="border-0">
          <td id="L536" class="blob-num border-0 px-3 py-0 color-bg-default" data-line-number="536"></td>
          <td id="LC536" class="blob-code border-0 px-3 py-0 color-bg-default blob-code-inner js-file-line"> <span class="pl-c"><span class="pl-c">#</span> FIXME: This code is completely invalid!!!</span> </td>
        </tr>
    </tbody></table>
  </div>
</div>
<br>
<div class="Box Box--condensed my-2">
  <div class="Box-header f6">
    <p class="mb-0 text-bold">
      <a href="https://github.com/JuliaLang/julia/blob/54adf2193a6ea1b10cd1a184a7ba863aa985eede/stdlib/LinearAlgebra/src/matmul.jl#L558">julia/stdlib/LinearAlgebra/src/matmul.jl</a>
    </p>
    <p class="mb-0 color-fg-muted">
         Line 558
      in
      <a data-pjax="true" class="commit-tease-sha" href="/JuliaLang/julia/commit/54adf2193a6ea1b10cd1a184a7ba863aa985eede">54adf21</a>
    </p>
  </div>
  <div itemprop="text" class="Box-body p-0 blob-wrapper blob-wrapper-embedded data">
    <table class="highlight tab-size mb-0 js-file-line-container" data-tab-size="8" data-paste-markdown-skip="">

        <tbody><tr class="border-0">
          <td id="L558" class="blob-num border-0 px-3 py-0 color-bg-default" data-line-number="558"></td>
          <td id="LC558" class="blob-code border-0 px-3 py-0 color-bg-default blob-code-inner js-file-line"> <span class="pl-c"><span class="pl-c">#</span> FIXME: This code is completely invalid!!!</span> </td>
        </tr>
    </tbody></table>
  </div>
</div>
<p></p>
<p dir="auto">I stumbled upon these two comments while perusing the base linalg code. Related statement in <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="261178317" data-permission-text="Title is private" data-url="https://github.com/JuliaLang/julia/issues/23914" data-hovercard-type="pull_request" data-hovercard-url="/JuliaLang/julia/pull/23914/hovercard" href="https://github.com/JuliaLang/julia/pull/23914">#23914</a>, where they were introduced:</p>
<blockquote>
<p dir="auto">Also marked a few even more invalid places where managed pointer is passed to unsafe_wrap (the fix for those will be much more involved).</p>
</blockquote>
<p dir="auto">Not terribly reassuring seeing this in production code, so I figured it deserved an open issue.</p>
<p dir="auto">At our centre we've just had a talk about Julia, and many of our users are<br>
interested in starting to experiment with using Julia for some of their<br>
work.</p>
<p dir="auto">I'd love to install Julia system-wide on our cluster to help them get<br>
started (especially since we try to link it with our local fast numerical<br>
libraries), but I'd like to update the package every now and then without<br>
changing it from under them.</p>
<p dir="auto">We usually do this with modules, creating new installation directories for<br>
each "version", and therein lies a bit of a stumbling block; I'd like to be<br>
able to describe which version they're using in a more consistent way than<br>
the build date, or, worse, something like<br>
<a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/JuliaLang/julia/commit/27bbad69c94685299c9db525442757934d322fe5/hovercard" href="https://github.com/JuliaLang/julia/commit/27bbad69c94685299c9db525442757934d322fe5"><tt>27bbad6</tt></a>.</p>
<p dir="auto">Is there any near term plans to start having tags for release numbers?</p>