Built site for gh-pages

.nojekyll

@@ -1 +1 @@
-4ec2d414
+691092e3

fprog.html

@@ -815,8 +815,8 @@ <h3 data-number="6.2.1" class="anchored" data-anchor-id="functions-are-first-cla
 <div class="sourceCode cell-code" id="cb74"><pre class="sourceCode r code-with-copy"><code class="sourceCode r"><span id="cb74-1"><a href="#cb74-1" aria-hidden="true" tabindex="-1"></a>chronicler<span class="sc">::</span><span class="fu">read_log</span>(result)</span></code><button title="Copy to Clipboard" class="code-copy-button"><i class="bi"></i></button></pre></div>
 <div class="cell-output cell-output-stdout">
 <pre><code>[1] "Complete log:"                                                                                
-[2] "NOK! sqrt() ran unsuccessfully with following exception: NaNs produced at 2024-04-01 12:29:54"
-[3] "Total running time: 0.000818967819213867 secs"                                                </code></pre>
+[2] "NOK! sqrt() ran unsuccessfully with following exception: NaNs produced at 2024-04-01 12:34:30"
+[3] "Total running time: 0.000924110412597656 secs"                                                </code></pre>
 </div>
 </div>
 <p>The <code>{purrr}</code> package also comes with function factories that you might find useful (<code>{possibly}</code>, <code>{safely}</code> and <code>{quietly}</code>).</p>
@@ -1679,7 +1679,7 @@ <h3 data-number="6.4.1" class="anchored" data-anchor-id="base-capabilities"><spa
 <div class="cell-output cell-output-stdout">
 <pre><code>function (x, ...) 
 UseMethod("print")
-&lt;bytecode: 0x55717af9bfe0&gt;
+&lt;bytecode: 0x55fbf0d92200&gt;
 &lt;environment: namespace:base&gt;</code></pre>
 </div>
 </div>
@@ -1723,7 +1723,7 @@ <h3 data-number="6.4.1" class="anchored" data-anchor-id="base-capabilities"><spa
     }
     invisible(x)
 }
-&lt;bytecode: 0x55717cdda108&gt;
+&lt;bytecode: 0x55fbf2bd0258&gt;
 &lt;environment: namespace:base&gt;</code></pre>
 </div>
 </div>

packages.html

@@ -560,7 +560,7 @@ <h2 data-number="11.3" class="anchored" data-anchor-id="turning-our-rmds-into-a-
 <span id="cb15-4"><a href="#cb15-4" aria-hidden="true" tabindex="-1"></a><span class="co">#' @importFrom stringr str_trim</span></span>
 <span id="cb15-5"><a href="#cb15-5" aria-hidden="true" tabindex="-1"></a><span class="co">#' @importFrom janitor clean_names</span></span>
 <span id="cb15-6"><a href="#cb15-6" aria-hidden="true" tabindex="-1"></a><span class="co">#' @importFrom purrr map_dfr</span></span></code><button title="Copy to Clipboard" class="code-copy-button"><i class="bi"></i></button></pre></div>
-<p>This is important, because the statements will write the dependencies into the package’s <code>NAMESPACE</code> file. This file is important, because any function defined there will be available to your package’s functions when you load the package. So if your function use <code>dplyr::mutate()</code> for example, your package needs to know where to look for <code>mutate()</code>. This is where the <code>NAMESPACE</code> file comes into play. Take the opportunity to list the dependencies of your function to review them: maybe you’re using a package for a single dependency that you could easily remove. For example, I’m using <code>stringr::str_trim()</code> to remove whitespace around characters. But I could be using the base R function <code>trimws()</code> instead, which would remove this dependency. I’m going to keep it here, because I’m lazy though. It might seem like extra work to add these statements. But you have to see it this way: you are writing the functions here, once, that need to be available to your functions for them to work. The alternative is to have to write:</p>
+<p>This is important, because the statements will write the dependencies into the package’s <code>NAMESPACE</code> file. This file is important, because any function defined there will be available to your package’s functions when you load the package. So if your function uses <code>dplyr::mutate()</code> for example, your package needs to know where to look for <code>mutate()</code>. This is where the <code>NAMESPACE</code> file comes into play. Take the opportunity to list the dependencies of your function to review them: maybe you’re using a package for a single dependency that you could easily remove. For example, I’m using <code>stringr::str_trim()</code> to remove whitespace around characters. But I could be using the base R function <code>trimws()</code> instead, which would remove this dependency. I’m going to keep it here, because I’m lazy though. It might seem like extra work to add these statements. But you have to see it this way: you are writing the functions here, once, that need to be available to your functions for them to work. The alternative is to have to write:</p>
 <div class="cell">
 <div class="sourceCode cell-code" id="cb16"><pre class="sourceCode r code-with-copy"><code class="sourceCode r"><span id="cb16-1"><a href="#cb16-1" aria-hidden="true" tabindex="-1"></a><span class="fu">library</span>(<span class="st">"readxl"</span>)</span>
 <span id="cb16-2"><a href="#cb16-2" aria-hidden="true" tabindex="-1"></a><span class="fu">library</span>(<span class="st">"utils"</span>)</span>