simple-future 1.0.0.pre3 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 3cba5eaf0775a2efbd7599fbc8a4be6a6a4b4b66
-  data.tar.gz: 4c714ad93fc19cf752ac13788afbe02c2eea1d2a
+  metadata.gz: 1df9f1b810af6a00ce3b5e97eaae569fab269360
+  data.tar.gz: 019574a38b467f2d60f6adb0692e96fb07a9b47f
 SHA512:
-  metadata.gz: d051b9f277e6b611d402580fadfe681742b0b763fd9c0c4c33481ed15b35f2fa6c90d778c1e9a149eb602b31aa408a758cf3764347b3d6e0190f2cc8b2e23982
-  data.tar.gz: 20229518589103a9a2c4bb338085b010e635c315f5dbed6000e849a02135a9714c2f3dda06bd55dabf6e9b4657fa48ecd41bada6560df5eee9d39f52dafeffbc
+  metadata.gz: 434b5e65ca6b30c698369d4564caae4fd1285f315d320c4a26301adeafe3c51ecb72108736a630b7e013e545ca146ed8ef12d724684f14609321f863bcb346f3
+  data.tar.gz: 1292d0877b4f0cfffacf9662490354a153604e66849e239d4456af839b4adcfed1f28df49adf1533fb6594a33e3a88da25f0ec290671fbb99d4ac67ed951138c

data/.yardopts

@@ -0,0 +1,3 @@
+--markup markdown
+--readme README.md
+lib/*.rb

data/doc/SimpleFuture.html

@@ -101,21 +101,21 @@
 
 <h2>Overview</h2><div class="docstring">
   <div class="discussion">
-    
-<p>A container holding the (eventual) result of a forked child process once
-that process finishes. The child process executes the code block that must
-be passed to the constructor:</p>
+    <p>A container holding the (eventual) result of a forked child process
+once that process finishes.  The child process executes the code
+block that must be passed to the constructor:</p>
 
 <pre class="code ruby"><code class="ruby">  sf = SimpleFuture.new { do_slow_thing }
   ... do stuff ...
-  use(sf.value)</code></pre>
+  use(sf.value)
+</code></pre>
 
 <p>The code block <strong>must</strong> return a value that can be encoded by
 <code>Marshal</code> and <strong>must not</strong> exit prematurely.</p>
 
 <p>Exceptions thrown inside the block will trigger a
-<code>SimpleFuture::ChildError</code> in the parent process but that
-exception will contain the original in its <code>cause</code> field.</p>
+<code>SimpleFuture::ChildError</code> in the parent process but that exception
+will contain the original in its <code>cause</code> field.</p>
 
 
   </div>
@@ -165,8 +165,7 @@ exception will contain the original in its <code>cause</code> field.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>Test if all instances created so far have run to completion.</p>
+    <span class="summary_desc"><div class='inline'><p>Test if all instances created so far have run to completion.</p>
 </div></span>
   
 </li>
@@ -189,8 +188,7 @@ exception will contain the original in its <code>cause</code> field.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>Return the maximum number of concurrent child processes allowed.</p>
+    <span class="summary_desc"><div class='inline'><p>Return the maximum number of concurrent child processes allowed.</p>
 </div></span>
   
 </li>
@@ -213,8 +211,7 @@ exception will contain the original in its <code>cause</code> field.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>Set the maximum number of concurrent child processes allowed.</p>
+    <span class="summary_desc"><div class='inline'><p>Set the maximum number of concurrent child processes allowed.</p>
 </div></span>
   
 </li>
@@ -237,9 +234,7 @@ exception will contain the original in its <code>cause</code> field.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>Wait until all child processes have run to completion and recover their
-results.</p>
+    <span class="summary_desc"><div class='inline'><p>Wait until all child processes have run to completion and recover their results.</p>
 </div></span>
   
 </li>
@@ -271,9 +266,7 @@ results.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>Check if the child process has finished evaluating the block and has a
-result ready.</p>
+    <span class="summary_desc"><div class='inline'><p>Check if the child process has finished evaluating the block and has a result ready.</p>
 </div></span>
   
 </li>
@@ -296,8 +289,7 @@ result ready.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>Test if the child process has finished and its result is available.</p>
+    <span class="summary_desc"><div class='inline'><p>Test if the child process has finished and its result is available.</p>
 </div></span>
   
 </li>
@@ -322,9 +314,7 @@ result ready.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>In addition to creating a new <code>SimpleFuture</code>, the constructor
-creates a child process and evaluates <code>action</code> in it.</p>
+    <span class="summary_desc"><div class='inline'><p>In addition to creating a new <code>SimpleFuture</code>, the constructor creates a child process and evaluates <code>action</code> in it.</p>
 </div></span>
   
 </li>
@@ -347,9 +337,7 @@ creates a child process and evaluates <code>action</code> in it.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>Return the result of the child process, blocking if it is not yet
-available.</p>
+    <span class="summary_desc"><div class='inline'><p>Return the result of the child process, blocking if it is not yet available.</p>
 </div></span>
   
 </li>
@@ -372,9 +360,7 @@ available.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>Block until the child process finishes, recover its result and clean up the
-process.</p>
+    <span class="summary_desc"><div class='inline'><p>Block until the child process finishes, recover its result and clean up the process.</p>
 </div></span>
   
 </li>
@@ -397,11 +383,10 @@ process.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>In addition to creating a new <code>SimpleFuture</code>, the constructor
-creates a child process and evaluates <code>action</code> in it. If the
-maximum number of child processes would be exceeded, it will block until a
-process finishes.</p>
+    <p>In addition to creating a new <code>SimpleFuture</code>, the constructor
+creates a child process and evaluates <code>action</code> in it.  If the
+maximum number of child processes would be exceeded, it will block
+until a process finishes.</p>
 
 
   </div>
@@ -462,11 +447,10 @@ process finishes.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Test if all instances created so far have run to completion. As a side
-effect, it will also call <code>wait</code> on instances whose child
+    <p>Test if all instances created so far have run to completion.  As a
+side effect, it will also call <code>wait</code> on instances whose child
 processes are running but have finished (i.e. their
-<code>check_if_ready</code> would return true.) This lets you use it as a
+<code>check_if_ready</code> would return true.)  This lets you use it as a
 non-blocking way to clean up the remaining children.</p>
 
 
@@ -522,8 +506,7 @@ non-blocking way to clean up the remaining children.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Return the maximum number of concurrent child processes allowed.</p>
+    <p>Return the maximum number of concurrent child processes allowed.</p>
 
 
   </div>
@@ -559,12 +542,11 @@ non-blocking way to clean up the remaining children.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Set the maximum number of concurrent child processes allowed. If set to
-less than 1, it is interpreted as meaning no limit.</p>
+    <p>Set the maximum number of concurrent child processes allowed.  If
+set to less than 1, it is interpreted as meaning no limit.</p>
 
-<p>It is initially set to the number of available cores as provided by the
-<code>Etc</code> module.</p>
+<p>It is initially set to the number of available cores as provided
+by the <code>Etc</code> module.</p>
 
 
   </div>
@@ -604,10 +586,10 @@ less than 1, it is interpreted as meaning no limit.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Wait until all child processes have run to completion and recover their
-results. Programs should call this before exiting if there is a chance that
-an instance was created without having <code>wait</code> called on it.</p>
+    <p>Wait until all child processes have run to completion and recover
+their results.  Programs should call this before exiting if there
+is a chance that an instance was created without having <code>wait</code>
+called on it.</p>
 
 
   </div>
@@ -657,15 +639,14 @@ an instance was created without having <code>wait</code> called on it.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Check if the child process has finished evaluating the block and has a
-result ready. If <code>check_if_ready</code> returns <code>true</code>,
-<code>wait</code> will not block when called.</p>
+    <p>Check if the child process has finished evaluating the block and
+has a result ready.  If <code>check_if_ready</code> returns <code>true</code>, <code>wait</code>
+will not block when called.</p>
 
-<p>Note: <code>check_if_ready</code> tests if there&#39;s data on the pipe to
-the child process to see if it has finished. A sufficiently evil child
-block might be able to cause a true result while still blocking
-<code>wait</code>.</p>
+<p>Note: <code>check_if_ready</code> tests if there&#39;s data on the pipe to the
+child process to see if it has finished.  A sufficiently evil
+child block might be able to cause a true result while still
+blocking <code>wait</code>.</p>
 
 <p>Don&#39;t do that.</p>
 
@@ -726,12 +707,12 @@ block might be able to cause a true result while still blocking
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Test if the child process has finished and its result is available.</p>
+    <p>Test if the child process has finished and its result is
+available.</p>
 
-<p>Note that this will only be true after a call to <code>wait</code> (i.e.
-the child process finished <strong>and</strong> its result has been
-retrieved.) If you want to see if the result is (probably) available, use
+<p>Note that this will only be true after a call to <code>wait</code> (i.e. the
+child process finished <strong>and</strong> its result has been retrieved.)  If
+you want to see if the result is (probably) available, use
 <code>check_if_ready</code>.</p>
 
 
@@ -781,9 +762,8 @@ retrieved.) If you want to see if the result is (probably) available, use
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Return the result of the child process, blocking if it is not yet
-available. Blocking is done by calling <code>wait</code>, so the process
+    <p>Return the result of the child process, blocking if it is not yet
+available.  Blocking is done by calling <code>wait</code>, so the process
 will be cleaned up.</p>
 
 
@@ -826,15 +806,13 @@ will be cleaned up.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Block until the child process finishes, recover its result and clean up the
-process. <code>wait</code> <strong>must</strong> be called for each
+    <p>Block until the child process finishes, recover its result and
+clean up the process.  <code>wait</code> <strong>must</strong> be called for each
 <code>SimpleFuture</code> to prevent zombie processes. In practice, this is
-rarely a problem since <code>value</code> calls <code>wait</code> and you
-usually want to get all of the values. See <code>wait_for_all</code>.</p>
+rarely a problem since <code>value</code> calls <code>wait</code> and you usually want
+to get all of the values.  See <code>wait_for_all</code>.</p>
 
-<p>It is safe to call <code>wait</code> multiple times on a
-<code>SimpleFuture</code>.</p>
+<p>It is safe to call <code>wait</code> multiple times on a <code>SimpleFuture</code>.</p>
 
 
   </div>
@@ -852,8 +830,7 @@ usually want to get all of the values. See <code>wait_for_all</code>.</p>
       
       
         &mdash;
-        <div class='inline'>
-<p>The child process raised an uncaught exception.</p>
+        <div class='inline'><p>The child process raised an uncaught exception.</p>
 </div>
       
     </li>
@@ -866,8 +843,7 @@ usually want to get all of the values. See <code>wait_for_all</code>.</p>
       
       
         &mdash;
-        <div class='inline'>
-<p>Marshal cannot encode the result</p>
+        <div class='inline'><p>Marshal cannot encode the result</p>
 </div>
       
     </li>
@@ -880,8 +856,7 @@ usually want to get all of the values. See <code>wait_for_all</code>.</p>
       
       
         &mdash;
-        <div class='inline'>
-<p>An error occurred in the IPC system or child process.</p>
+        <div class='inline'><p>An error occurred in the IPC system or child process.</p>
 </div>
       
     </li>
@@ -988,9 +963,9 @@ usually want to get all of the values. See <code>wait_for_all</code>.</p>
 </div>
 
       <div id="footer">
-  Generated on Wed Jan 17 18:42:40 2018 by
+  Generated on Wed Jan 17 21:04:35 2018 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.12 (ruby-2.4.3).
+  0.9.12 (ruby-2.3.1).
 </div>
 
     </div>

data/doc/SimpleFuture/ChildError.html

@@ -105,9 +105,8 @@
 
 <h2>Overview</h2><div class="docstring">
   <div class="discussion">
-    
-<p>Exception class for the case where an uncaught exception is thrown in the
-child process.</p>
+    <p>Exception class for the case where an uncaught exception is thrown
+in the child process.</p>
 
 
   </div>
@@ -144,8 +143,7 @@ child process.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>If the child process threw an exception, this is it.</p>
+    <span class="summary_desc"><div class='inline'><p>If the child process threw an exception, this is it.</p>
 </div></span>
   
 </li>
@@ -183,8 +181,7 @@ child process.</p>
   
 
   
-    <span class="summary_desc"><div class='inline'>
-<p>A new instance of ChildError.</p>
+    <span class="summary_desc"><div class='inline'><p>A new instance of ChildError.</p>
 </div></span>
   
 </li>
@@ -236,8 +233,7 @@ child process.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>Returns a new instance of ChildError</p>
+    <p>Returns a new instance of ChildError</p>
 
 
   </div>
@@ -256,8 +252,7 @@ child process.</p>
       
       
         &mdash;
-        <div class='inline'>
-<p>The exception text.</p>
+        <div class='inline'><p>The exception text.</p>
 </div>
       
     </li>
@@ -274,8 +269,7 @@ child process.</p>
       
       
         &mdash;
-        <div class='inline'>
-<p>If valid, the exception raised in the child</p>
+        <div class='inline'><p>If valid, the exception raised in the child</p>
 </div>
       
     </li>
@@ -324,9 +318,8 @@ child process.</p>
   
 </h3><div class="docstring">
   <div class="discussion">
-    
-<p>If the child process threw an exception, this is it. Otherwise, it&#39;s
-nil.</p>
+    <p>If the child process threw an exception, this is it.  Otherwise,
+it&#39;s nil.</p>
 
 
   </div>
@@ -401,9 +394,9 @@ nil.</p>
 </div>
 
       <div id="footer">
-  Generated on Wed Jan 17 18:42:40 2018 by
+  Generated on Wed Jan 17 21:04:35 2018 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.12 (ruby-2.4.3).
+  0.9.12 (ruby-2.3.1).
 </div>
 
     </div>

data/doc/SimpleFuture/Error.html

@@ -103,9 +103,9 @@
 
 <h2>Overview</h2><div class="docstring">
   <div class="discussion">
-    
-<p>Exception class for errors related to SimpleFuture. All exceptions thrown
-by SimpleFuture are either <code>Error</code> or a subclass.</p>
+    <p>Exception class for errors related to SimpleFuture.  All
+exceptions thrown by SimpleFuture are either <code>Error</code> or a
+subclass.</p>
 
 
   </div>
@@ -130,9 +130,9 @@ by SimpleFuture are either <code>Error</code> or a subclass.</p>
 </div>
 
       <div id="footer">
-  Generated on Wed Jan 17 18:42:40 2018 by
+  Generated on Wed Jan 17 21:04:35 2018 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.12 (ruby-2.4.3).
+  0.9.12 (ruby-2.3.1).
 </div>
 
     </div>

data/doc/SimpleFuture/ResultTypeError.html

@@ -105,12 +105,11 @@
 
 <h2>Overview</h2><div class="docstring">
   <div class="discussion">
-    
-<p>Exception class for the case(s) where the result is of a type that
+    <p>Exception class for the case(s) where the result is of a type that
 can&#39;t be returned (e.g. because it&#39;s one of the types
-<code>Marshal.dump()</code> fails on). This can also apply to exceptions;
-if an exception object holds an unmarshallable value, you&#39;ll get one of
-these instead of a <code>SimpleFuture::ChildError</code>.</p>
+<code>Marshal.dump()</code> fails on).  This can also apply to exceptions; if
+an exception object holds an unmarshallable value, you&#39;ll get one
+of these instead of a <code>SimpleFuture::ChildError</code>.</p>
 
 
   </div>
@@ -137,9 +136,9 @@ these instead of a <code>SimpleFuture::ChildError</code>.</p>
 </div>
 
       <div id="footer">
-  Generated on Wed Jan 17 18:42:40 2018 by
+  Generated on Wed Jan 17 21:04:35 2018 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.12 (ruby-2.4.3).
+  0.9.12 (ruby-2.3.1).
 </div>
 
     </div>

data/doc/_index.html

@@ -142,9 +142,9 @@
 </div>
 
       <div id="footer">
-  Generated on Wed Jan 17 18:42:39 2018 by
+  Generated on Wed Jan 17 21:04:35 2018 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.12 (ruby-2.4.3).
+  0.9.12 (ruby-2.3.1).
 </div>
 
     </div>

data/doc/file.README.html

@@ -57,42 +57,37 @@
         <div class="clear"></div>
       </div>
 
-      <div id="content"><div id='filecontents'>
-<h1 id="label-SimpleFuture-3A+Simple-2C+Process-based+Concurrency">SimpleFuture: Simple, Process-based Concurrency</h1>
+      <div id="content"><div id='filecontents'><h1>SimpleFuture: Simple, Process-based Concurrency</h1>
 
-<p><code>SimpleFuture</code> is a Ruby module that gives you pretty good
-concurrency without a lot of work. It doesn&#39;t use threads and so will
-avoid their common pitfalls as well working on Rubies that don&#39;t
-support them.</p>
+<p><code>SimpleFuture</code> is a Ruby module that gives you pretty good concurrency
+without a lot of work.  It doesn&#39;t use threads and so will avoid their
+common pitfalls as well working on Rubies that don&#39;t support them.</p>
 
-<p>It is a simple implementation of <a
-href="https://en.wikipedia.org/wiki/Futures_and_promises">Future</a>
-construct.</p>
+<p>It is a simple implementation of <a href="https://en.wikipedia.org/wiki/Futures_and_promises">Future</a> construct.</p>
 
-<h2 id="label-Resources">Resources</h2>
-<ul><li>
-<p><a href="https://github.com/suetanvil/simple-future/">Home Page</a></p>
-</li><li>
-<p><a href="https://github.com/suetanvil/simple-future/issues">Issues</a></p>
-</li><li>
-<p><a href="http://www.rubydoc.info/gems/simple-future">Reference Docs</a></p>
-</li></ul>
+<h2>Resources</h2>
 
-<h2 id="label-Basic+idea">Basic idea</h2>
+<ul>
+<li><a href="https://github.com/suetanvil/simple-future/">Home Page</a></li>
+<li><a href="https://github.com/suetanvil/simple-future/issues">Issues</a></li>
+<li><a href="http://www.rubydoc.info/gems/simple-future">Reference Docs</a></li>
+</ul>
 
-<p>Suppose you need to do a bunch of long-running things concurrently (e.g.
-transcode a bunch of videos) and you don&#39;t want to have to deal with
-threads.</p>
+<h2>Basic idea</h2>
+
+<p>Suppose you need to do a bunch of long-running things concurrently
+(e.g. transcode a bunch of videos) and you don&#39;t want to have to deal
+with threads.</p>
 
 <p>The easy thing to do is fork a subprocess for each item and then use
 <code>Marshal</code> and <code>IO.pipe</code> to retrieve the result(s).</p>
 
-<p>That&#39;s pretty much what <code>SimpleFuture</code> does for you. You
-pass it a block and it runs it in a forked child and gives you back the
-result when it&#39;s ready. And as a bonus, it will limit the number of
-children it creates at one time, so you don&#39;t have to.</p>
+<p>That&#39;s pretty much what <code>SimpleFuture</code> does for you.  You pass it a
+block and it runs it in a forked child and gives you back the result
+when it&#39;s ready.  And as a bonus, it will limit the number of children
+it creates at one time, so you don&#39;t have to.</p>
 
-<h2 id="label-Those+videos-2C+for+example">Those videos, for example</h2>
+<h2>Those videos, for example</h2>
 
 <p>So let&#39;s say you&#39;re transcoding a bunch of (legally obtained) video
 files:</p>
@@ -104,7 +99,7 @@ files:</p>
 </code></pre>
 
 <p>This is nice and simple, but it isn&#39;t taking advantage of the zillions
-of cores you have on your fancy modern workstation. So you use
+of cores you have on your fancy modern workstation.  So you use
 <code>SimpleFuture</code>:</p>
 
 <pre class="code ruby"><code class="ruby"><span class='kw'>for</span> <span class='id identifier rubyid_vid'>vid</span> <span class='kw'>in</span> <span class='const'>Dir</span><span class='period'>.</span><span class='id identifier rubyid_glob'>glob</span><span class='lparen'>(</span><span class='tstring'><span class='tstring_beg'>&#39;</span><span class='tstring_content'>*.mp4</span><span class='tstring_end'>&#39;</span></span><span class='rparen'>)</span>
@@ -114,22 +109,21 @@ of cores you have on your fancy modern workstation. So you use
 <span class='const'><span class='object_link'><a href="SimpleFuture.html" title="SimpleFuture (class)">SimpleFuture</a></span></span><span class='period'>.</span><span class='id identifier rubyid_wait_for_all'><span class='object_link'><a href="SimpleFuture.html#wait_for_all-class_method" title="SimpleFuture.wait_for_all (method)">wait_for_all</a></span></span>
 </code></pre>
 
-<p>And this will do what you want. In particular, it limits itself to one
-process per CPU core so you don&#39;t thrash your system. (You can change
-this limit via <code>SimpleFuture.max_tasks</code>.)</p>
+<p>And this will do what you want.  In particular, it limits itself to
+one process per CPU core so you don&#39;t thrash your system.  (You can
+change this limit via <code>SimpleFuture.max_tasks</code>.)</p>
 
-<h2 id="label-Wait+for+it">Wait for it</h2>
+<h2>Wait for it</h2>
 
-<p>Notice that we end the script with <code>wait_for_all</code>. This is
-because each <code>SimpleFuture</code> needs to have its <code>wait</code>
-method called at some point. This is what <code>wait_for_all</code> does.
-(<code>SimpleFuture.new</code> will also sometimes call an existing
-instance&#39;s <code>wait</code> but you can&#39;t depend on that.)</p>
+<p>Notice that we end the script with <code>wait_for_all</code>.  This is because
+each <code>SimpleFuture</code> needs to have its <code>wait</code> method called at some
+point.  This is what <code>wait_for_all</code> does.  (<code>SimpleFuture.new</code> will
+also sometimes call an existing instance&#39;s <code>wait</code> but you can&#39;t depend
+on that.)</p>
 
 <p>Since <code>wait</code> blocks until the child process finishes, so will
-<code>wait_for_all</code>. If you don&#39;t like that, you can also use
-<code>all_done?</code>; this won&#39;t block so you can do other stuff
-while waiting:</p>
+<code>wait_for_all</code>.  If you don&#39;t like that, you can also use <code>all_done?</code>;
+this won&#39;t block so you can do other stuff while waiting:</p>
 
 <pre class="code ruby"><code class="ruby"><span class='kw'>while</span> <span class='op'>!</span><span class='const'><span class='object_link'><a href="SimpleFuture.html" title="SimpleFuture (class)">SimpleFuture</a></span></span><span class='period'>.</span><span class='id identifier rubyid_all_done?'><span class='object_link'><a href="SimpleFuture.html#all_done%3F-class_method" title="SimpleFuture.all_done? (method)">all_done?</a></span></span>
     <span class='id identifier rubyid_puts'>puts</span> <span class='tstring'><span class='tstring_beg'>&quot;</span><span class='tstring_content'>Waiting for child processes to finish.</span><span class='tstring_end'>&quot;</span></span>
@@ -137,15 +131,15 @@ while waiting:</p>
 <span class='kw'>end</span>
 </code></pre>
 
-<p>By the way, it&#39;s harmless to call <code>wait_for_all</code> if nothing
-is running so it&#39;s often good practice to just call it before quitting.</p>
+<p>By the way, it&#39;s harmless to call <code>wait_for_all</code> if nothing is running
+so it&#39;s often good practice to just call it before quitting.</p>
 
-<h2 id="label-I+need+answers">I need answers</h2>
+<h2>I need answers</h2>
 
-<p>But let&#39;s say that <code>transcode()</code> also returns an important
-result such as the compression ratio and you want to know the average. This
-means that you need to get a result back from the child process.
-Fortunately, <code>SimpleFuture</code> handles this.</p>
+<p>But let&#39;s say that <code>transcode()</code> also returns an important result such
+as the compression ratio and you want to know the average. This means
+that you need to get a result back from the child
+process. Fortunately, <code>SimpleFuture</code> handles this.</p>
 
 <p>First, we need to keep all of the <code>SimpleFuture</code> objects:</p>
 
@@ -167,13 +161,13 @@ Fortunately, <code>SimpleFuture</code> handles this.</p>
     <span class='id identifier rubyid_ratios'>ratios</span><span class='period'>.</span><span class='id identifier rubyid_size'>size</span> <span class='op'>&gt;</span> <span class='int'>0</span>
 </code></pre>
 
-<p>Note that we&#39;re not calling <code>wait_for_all</code> here. This is
-because <code>value</code> already calls <code>wait</code> and since it
-gets called on each <code>SimpleFuture</code>, we know for sure that all
-child processes have been cleaned up.</p>
+<p>Note that we&#39;re not calling <code>wait_for_all</code> here.  This is because
+<code>value</code> already calls <code>wait</code> and since it gets called on each
+<code>SimpleFuture</code>, we know for sure that all child processes have been
+cleaned up.</p>
 
-<p>Also, it may be tempting to merge the loop and the map above but this is a
-<strong>bad idea</strong>:</p>
+<p>Also, it may be tempting to merge the loop and the map above but this
+is a <strong>bad idea</strong>:</p>
 
 <pre class="code ruby"><code class="ruby"><span class='id identifier rubyid_ratios'>ratios</span> <span class='op'>=</span> <span class='lbracket'>[</span><span class='rbracket'>]</span>
 <span class='kw'>for</span> <span class='id identifier rubyid_vid'>vid</span> <span class='kw'>in</span> <span class='const'>Dir</span><span class='period'>.</span><span class='id identifier rubyid_glob'>glob</span><span class='lparen'>(</span><span class='tstring'><span class='tstring_beg'>&#39;</span><span class='tstring_content'>*.mp4</span><span class='tstring_end'>&#39;</span></span><span class='rparen'>)</span>
@@ -182,71 +176,73 @@ child processes have been cleaned up.</p>
 </span><span class='kw'>end</span>
 </code></pre>
 
-<p>Because <code>wait</code> stops until the child process finishes,
-you&#39;re effectively going back to single-threaded processing. You need
-to create a collection of <code>SimpleFuture</code>s first and
-<em>then</em> <code>wait</code> on them.</p>
+<p>Because <code>wait</code> stops until the child process finishes, you&#39;re
+effectively going back to single-threaded processing.  You need to
+create a collection of <code>SimpleFuture</code>s first and <em>then</em> <code>wait</code> on
+them.</p>
 
-<h2 id="label-Oooopsie-21">Oooopsie!</h2>
+<h2>Oooopsie!</h2>
 
-<p><code>SimpleFuture</code> tries to only throw exceptions in two cases:
-something is wrong with your code or something has gone wrong beyond its
-control (e.g. Ruby crashed). In either case, the right thing at this point
-is usually to quit. (If that&#39;s not an option, the rubydocs will give
-you the gory details on what throws what.)</p>
+<p><code>SimpleFuture</code> tries to only throw exceptions in two cases: something
+is wrong with your code or something has gone wrong beyond its control
+(e.g. Ruby crashed).  In either case, the right thing at this point is
+usually to quit. (If that&#39;s not an option, the rubydocs will give you
+the gory details on what throws what.)</p>
 
 <p>Generally, you should:</p>
-<ol><li>
-<p>Never quit the child process; always exit the block with a (simple, 
-Marshal-compatible) value.</p>
-</li><li>
-<p>Avoid throwing exceptions out of the child block unless it&#39;s to  avoid
-breaking rule 1.</p>
-</li></ol>
+
+<ol>
+<li>Never quit the child process; always exit the block with a (simple,
+Marshal-compatible) value.</li>
+<li>Avoid throwing exceptions out of the child block unless it&#39;s to
+avoid breaking rule 1.</li>
+</ol>
 
 <p>Also, you can probably use low-level systems methods to trick
-<code>SimpleFuture</code> into doing the wrong thing. Don&#39;t do that.</p>
+<code>SimpleFuture</code> into doing the wrong thing.  Don&#39;t do that.</p>
 
-<h2 id="label-Installation">Installation</h2>
+<h2>Installation</h2>
 
 <p>SimpleFuture is available as a gem:</p>
 
-<pre class="code ruby"><code class="ruby">$ [sudo] gem install simple-future</code></pre>
+<pre class="code ruby"><code class="ruby">$ [sudo] gem install simple-future
+</code></pre>
 
 <p>Source code is available at GitHub:</p>
 
 <pre class="code ruby"><code class="ruby">$ git clone https://github.com/suetanvil/simple-future.git
 $ cd simple-future
-$ rake</code></pre>
+$ rake
+</code></pre>
 
-<p>To build, you need to install <code>rake</code>, <code>rspec</code> and
-<code>yard</code>.</p>
+<p>To build, you need to install <code>rake</code>, <code>rspec</code> and <code>yard</code>.</p>
 
-<p>It should work on Ruby 2.2.0 or later, provided your Ruby/OS combination
-supports <code>Process.fork()</code>. To confirm this, evaluate</p>
+<p>It should work on Ruby 2.2.0 or later, provided your Ruby/OS
+combination supports <code>Process.fork()</code>.  To confirm this, evaluate</p>
 
 <pre class="code ruby"><code class="ruby"><span class='const'>Process</span><span class='period'>.</span><span class='id identifier rubyid_respond_to?'>respond_to?</span><span class='lparen'>(</span><span class='symbol'>:fork</span><span class='rparen'>)</span>      <span class='comment'># true
 </span></code></pre>
 
-<p>If it returns true, you&#39;re good to go. If not, the gem will noisily
+<p>If it returns true, you&#39;re good to go.  If not, the gem will noisily
 fail.</p>
 
-<h2 id="label-Bugs+and+Quirks">Bugs and Quirks</h2>
+<h2>Bugs and Quirks</h2>
 
-<p><code>SimpleFuture.new</code> will block if there are too many child
-processes. In this case, it waits for the <strong>oldest</strong> process
-to finish, even if other processes have finished in the meantime.</p>
+<p><code>SimpleFuture.new</code> will block if there are too many child processes.
+In this case, it waits for the <strong>oldest</strong> process to finish, even if
+other processes have finished in the meantime.</p>
 
 <p>The unit tests use <code>sleep</code> to give child processes a relatively
-predictable execution times and test based on that. This means there&#39;s
-a chance that the tests can fail on a sufficiently slow or overloaded
-system. (It&#39;s unlikely that this can happen in real life, though.)</p>
+predictable execution times and test based on that.  This means
+there&#39;s a chance that the tests can fail on a sufficiently slow or
+overloaded system.  (It&#39;s unlikely that this can happen in real life,
+though.)</p>
 </div></div>
 
       <div id="footer">
-  Generated on Wed Jan 17 18:42:40 2018 by
+  Generated on Wed Jan 17 21:04:35 2018 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.12 (ruby-2.4.3).
+  0.9.12 (ruby-2.3.1).
 </div>
 
     </div>

data/doc/index.html

@@ -57,42 +57,37 @@
         <div class="clear"></div>
       </div>
 
-      <div id="content"><div id='filecontents'>
-<h1 id="label-SimpleFuture-3A+Simple-2C+Process-based+Concurrency">SimpleFuture: Simple, Process-based Concurrency</h1>
+      <div id="content"><div id='filecontents'><h1>SimpleFuture: Simple, Process-based Concurrency</h1>
 
-<p><code>SimpleFuture</code> is a Ruby module that gives you pretty good
-concurrency without a lot of work. It doesn&#39;t use threads and so will
-avoid their common pitfalls as well working on Rubies that don&#39;t
-support them.</p>
+<p><code>SimpleFuture</code> is a Ruby module that gives you pretty good concurrency
+without a lot of work.  It doesn&#39;t use threads and so will avoid their
+common pitfalls as well working on Rubies that don&#39;t support them.</p>
 
-<p>It is a simple implementation of <a
-href="https://en.wikipedia.org/wiki/Futures_and_promises">Future</a>
-construct.</p>
+<p>It is a simple implementation of <a href="https://en.wikipedia.org/wiki/Futures_and_promises">Future</a> construct.</p>
 
-<h2 id="label-Resources">Resources</h2>
-<ul><li>
-<p><a href="https://github.com/suetanvil/simple-future/">Home Page</a></p>
-</li><li>
-<p><a href="https://github.com/suetanvil/simple-future/issues">Issues</a></p>
-</li><li>
-<p><a href="http://www.rubydoc.info/gems/simple-future">Reference Docs</a></p>
-</li></ul>
+<h2>Resources</h2>
 
-<h2 id="label-Basic+idea">Basic idea</h2>
+<ul>
+<li><a href="https://github.com/suetanvil/simple-future/">Home Page</a></li>
+<li><a href="https://github.com/suetanvil/simple-future/issues">Issues</a></li>
+<li><a href="http://www.rubydoc.info/gems/simple-future">Reference Docs</a></li>
+</ul>
 
-<p>Suppose you need to do a bunch of long-running things concurrently (e.g.
-transcode a bunch of videos) and you don&#39;t want to have to deal with
-threads.</p>
+<h2>Basic idea</h2>
+
+<p>Suppose you need to do a bunch of long-running things concurrently
+(e.g. transcode a bunch of videos) and you don&#39;t want to have to deal
+with threads.</p>
 
 <p>The easy thing to do is fork a subprocess for each item and then use
 <code>Marshal</code> and <code>IO.pipe</code> to retrieve the result(s).</p>
 
-<p>That&#39;s pretty much what <code>SimpleFuture</code> does for you. You
-pass it a block and it runs it in a forked child and gives you back the
-result when it&#39;s ready. And as a bonus, it will limit the number of
-children it creates at one time, so you don&#39;t have to.</p>
+<p>That&#39;s pretty much what <code>SimpleFuture</code> does for you.  You pass it a
+block and it runs it in a forked child and gives you back the result
+when it&#39;s ready.  And as a bonus, it will limit the number of children
+it creates at one time, so you don&#39;t have to.</p>
 
-<h2 id="label-Those+videos-2C+for+example">Those videos, for example</h2>
+<h2>Those videos, for example</h2>
 
 <p>So let&#39;s say you&#39;re transcoding a bunch of (legally obtained) video
 files:</p>
@@ -104,7 +99,7 @@ files:</p>
 </code></pre>
 
 <p>This is nice and simple, but it isn&#39;t taking advantage of the zillions
-of cores you have on your fancy modern workstation. So you use
+of cores you have on your fancy modern workstation.  So you use
 <code>SimpleFuture</code>:</p>
 
 <pre class="code ruby"><code class="ruby"><span class='kw'>for</span> <span class='id identifier rubyid_vid'>vid</span> <span class='kw'>in</span> <span class='const'>Dir</span><span class='period'>.</span><span class='id identifier rubyid_glob'>glob</span><span class='lparen'>(</span><span class='tstring'><span class='tstring_beg'>&#39;</span><span class='tstring_content'>*.mp4</span><span class='tstring_end'>&#39;</span></span><span class='rparen'>)</span>
@@ -114,22 +109,21 @@ of cores you have on your fancy modern workstation. So you use
 <span class='const'><span class='object_link'><a href="SimpleFuture.html" title="SimpleFuture (class)">SimpleFuture</a></span></span><span class='period'>.</span><span class='id identifier rubyid_wait_for_all'><span class='object_link'><a href="SimpleFuture.html#wait_for_all-class_method" title="SimpleFuture.wait_for_all (method)">wait_for_all</a></span></span>
 </code></pre>
 
-<p>And this will do what you want. In particular, it limits itself to one
-process per CPU core so you don&#39;t thrash your system. (You can change
-this limit via <code>SimpleFuture.max_tasks</code>.)</p>
+<p>And this will do what you want.  In particular, it limits itself to
+one process per CPU core so you don&#39;t thrash your system.  (You can
+change this limit via <code>SimpleFuture.max_tasks</code>.)</p>
 
-<h2 id="label-Wait+for+it">Wait for it</h2>
+<h2>Wait for it</h2>
 
-<p>Notice that we end the script with <code>wait_for_all</code>. This is
-because each <code>SimpleFuture</code> needs to have its <code>wait</code>
-method called at some point. This is what <code>wait_for_all</code> does.
-(<code>SimpleFuture.new</code> will also sometimes call an existing
-instance&#39;s <code>wait</code> but you can&#39;t depend on that.)</p>
+<p>Notice that we end the script with <code>wait_for_all</code>.  This is because
+each <code>SimpleFuture</code> needs to have its <code>wait</code> method called at some
+point.  This is what <code>wait_for_all</code> does.  (<code>SimpleFuture.new</code> will
+also sometimes call an existing instance&#39;s <code>wait</code> but you can&#39;t depend
+on that.)</p>
 
 <p>Since <code>wait</code> blocks until the child process finishes, so will
-<code>wait_for_all</code>. If you don&#39;t like that, you can also use
-<code>all_done?</code>; this won&#39;t block so you can do other stuff
-while waiting:</p>
+<code>wait_for_all</code>.  If you don&#39;t like that, you can also use <code>all_done?</code>;
+this won&#39;t block so you can do other stuff while waiting:</p>
 
 <pre class="code ruby"><code class="ruby"><span class='kw'>while</span> <span class='op'>!</span><span class='const'><span class='object_link'><a href="SimpleFuture.html" title="SimpleFuture (class)">SimpleFuture</a></span></span><span class='period'>.</span><span class='id identifier rubyid_all_done?'><span class='object_link'><a href="SimpleFuture.html#all_done%3F-class_method" title="SimpleFuture.all_done? (method)">all_done?</a></span></span>
     <span class='id identifier rubyid_puts'>puts</span> <span class='tstring'><span class='tstring_beg'>&quot;</span><span class='tstring_content'>Waiting for child processes to finish.</span><span class='tstring_end'>&quot;</span></span>
@@ -137,15 +131,15 @@ while waiting:</p>
 <span class='kw'>end</span>
 </code></pre>
 
-<p>By the way, it&#39;s harmless to call <code>wait_for_all</code> if nothing
-is running so it&#39;s often good practice to just call it before quitting.</p>
+<p>By the way, it&#39;s harmless to call <code>wait_for_all</code> if nothing is running
+so it&#39;s often good practice to just call it before quitting.</p>
 
-<h2 id="label-I+need+answers">I need answers</h2>
+<h2>I need answers</h2>
 
-<p>But let&#39;s say that <code>transcode()</code> also returns an important
-result such as the compression ratio and you want to know the average. This
-means that you need to get a result back from the child process.
-Fortunately, <code>SimpleFuture</code> handles this.</p>
+<p>But let&#39;s say that <code>transcode()</code> also returns an important result such
+as the compression ratio and you want to know the average. This means
+that you need to get a result back from the child
+process. Fortunately, <code>SimpleFuture</code> handles this.</p>
 
 <p>First, we need to keep all of the <code>SimpleFuture</code> objects:</p>
 
@@ -167,13 +161,13 @@ Fortunately, <code>SimpleFuture</code> handles this.</p>
     <span class='id identifier rubyid_ratios'>ratios</span><span class='period'>.</span><span class='id identifier rubyid_size'>size</span> <span class='op'>&gt;</span> <span class='int'>0</span>
 </code></pre>
 
-<p>Note that we&#39;re not calling <code>wait_for_all</code> here. This is
-because <code>value</code> already calls <code>wait</code> and since it
-gets called on each <code>SimpleFuture</code>, we know for sure that all
-child processes have been cleaned up.</p>
+<p>Note that we&#39;re not calling <code>wait_for_all</code> here.  This is because
+<code>value</code> already calls <code>wait</code> and since it gets called on each
+<code>SimpleFuture</code>, we know for sure that all child processes have been
+cleaned up.</p>
 
-<p>Also, it may be tempting to merge the loop and the map above but this is a
-<strong>bad idea</strong>:</p>
+<p>Also, it may be tempting to merge the loop and the map above but this
+is a <strong>bad idea</strong>:</p>
 
 <pre class="code ruby"><code class="ruby"><span class='id identifier rubyid_ratios'>ratios</span> <span class='op'>=</span> <span class='lbracket'>[</span><span class='rbracket'>]</span>
 <span class='kw'>for</span> <span class='id identifier rubyid_vid'>vid</span> <span class='kw'>in</span> <span class='const'>Dir</span><span class='period'>.</span><span class='id identifier rubyid_glob'>glob</span><span class='lparen'>(</span><span class='tstring'><span class='tstring_beg'>&#39;</span><span class='tstring_content'>*.mp4</span><span class='tstring_end'>&#39;</span></span><span class='rparen'>)</span>
@@ -182,71 +176,73 @@ child processes have been cleaned up.</p>
 </span><span class='kw'>end</span>
 </code></pre>
 
-<p>Because <code>wait</code> stops until the child process finishes,
-you&#39;re effectively going back to single-threaded processing. You need
-to create a collection of <code>SimpleFuture</code>s first and
-<em>then</em> <code>wait</code> on them.</p>
+<p>Because <code>wait</code> stops until the child process finishes, you&#39;re
+effectively going back to single-threaded processing.  You need to
+create a collection of <code>SimpleFuture</code>s first and <em>then</em> <code>wait</code> on
+them.</p>
 
-<h2 id="label-Oooopsie-21">Oooopsie!</h2>
+<h2>Oooopsie!</h2>
 
-<p><code>SimpleFuture</code> tries to only throw exceptions in two cases:
-something is wrong with your code or something has gone wrong beyond its
-control (e.g. Ruby crashed). In either case, the right thing at this point
-is usually to quit. (If that&#39;s not an option, the rubydocs will give
-you the gory details on what throws what.)</p>
+<p><code>SimpleFuture</code> tries to only throw exceptions in two cases: something
+is wrong with your code or something has gone wrong beyond its control
+(e.g. Ruby crashed).  In either case, the right thing at this point is
+usually to quit. (If that&#39;s not an option, the rubydocs will give you
+the gory details on what throws what.)</p>
 
 <p>Generally, you should:</p>
-<ol><li>
-<p>Never quit the child process; always exit the block with a (simple, 
-Marshal-compatible) value.</p>
-</li><li>
-<p>Avoid throwing exceptions out of the child block unless it&#39;s to  avoid
-breaking rule 1.</p>
-</li></ol>
+
+<ol>
+<li>Never quit the child process; always exit the block with a (simple,
+Marshal-compatible) value.</li>
+<li>Avoid throwing exceptions out of the child block unless it&#39;s to
+avoid breaking rule 1.</li>
+</ol>
 
 <p>Also, you can probably use low-level systems methods to trick
-<code>SimpleFuture</code> into doing the wrong thing. Don&#39;t do that.</p>
+<code>SimpleFuture</code> into doing the wrong thing.  Don&#39;t do that.</p>
 
-<h2 id="label-Installation">Installation</h2>
+<h2>Installation</h2>
 
 <p>SimpleFuture is available as a gem:</p>
 
-<pre class="code ruby"><code class="ruby">$ [sudo] gem install simple-future</code></pre>
+<pre class="code ruby"><code class="ruby">$ [sudo] gem install simple-future
+</code></pre>
 
 <p>Source code is available at GitHub:</p>
 
 <pre class="code ruby"><code class="ruby">$ git clone https://github.com/suetanvil/simple-future.git
 $ cd simple-future
-$ rake</code></pre>
+$ rake
+</code></pre>
 
-<p>To build, you need to install <code>rake</code>, <code>rspec</code> and
-<code>yard</code>.</p>
+<p>To build, you need to install <code>rake</code>, <code>rspec</code> and <code>yard</code>.</p>
 
-<p>It should work on Ruby 2.2.0 or later, provided your Ruby/OS combination
-supports <code>Process.fork()</code>. To confirm this, evaluate</p>
+<p>It should work on Ruby 2.2.0 or later, provided your Ruby/OS
+combination supports <code>Process.fork()</code>.  To confirm this, evaluate</p>
 
 <pre class="code ruby"><code class="ruby"><span class='const'>Process</span><span class='period'>.</span><span class='id identifier rubyid_respond_to?'>respond_to?</span><span class='lparen'>(</span><span class='symbol'>:fork</span><span class='rparen'>)</span>      <span class='comment'># true
 </span></code></pre>
 
-<p>If it returns true, you&#39;re good to go. If not, the gem will noisily
+<p>If it returns true, you&#39;re good to go.  If not, the gem will noisily
 fail.</p>
 
-<h2 id="label-Bugs+and+Quirks">Bugs and Quirks</h2>
+<h2>Bugs and Quirks</h2>
 
-<p><code>SimpleFuture.new</code> will block if there are too many child
-processes. In this case, it waits for the <strong>oldest</strong> process
-to finish, even if other processes have finished in the meantime.</p>
+<p><code>SimpleFuture.new</code> will block if there are too many child processes.
+In this case, it waits for the <strong>oldest</strong> process to finish, even if
+other processes have finished in the meantime.</p>
 
 <p>The unit tests use <code>sleep</code> to give child processes a relatively
-predictable execution times and test based on that. This means there&#39;s
-a chance that the tests can fail on a sufficiently slow or overloaded
-system. (It&#39;s unlikely that this can happen in real life, though.)</p>
+predictable execution times and test based on that.  This means
+there&#39;s a chance that the tests can fail on a sufficiently slow or
+overloaded system.  (It&#39;s unlikely that this can happen in real life,
+though.)</p>
 </div></div>
 
       <div id="footer">
-  Generated on Wed Jan 17 18:42:40 2018 by
+  Generated on Wed Jan 17 21:04:35 2018 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.12 (ruby-2.4.3).
+  0.9.12 (ruby-2.3.1).
 </div>
 
     </div>

data/doc/top-level-namespace.html

@@ -100,9 +100,9 @@
 </div>
 
       <div id="footer">
-  Generated on Wed Jan 17 18:42:40 2018 by
+  Generated on Wed Jan 17 21:04:35 2018 by
   <a href="http://yardoc.org" title="Yay! A Ruby Documentation Tool" target="_parent">yard</a>
-  0.9.12 (ruby-2.4.3).
+  0.9.12 (ruby-2.3.1).
 </div>
 
     </div>

data/simple-future.gemspec

@@ -1,8 +1,8 @@
 
 Gem::Specification.new do |s|
   s.name        = 'simple-future'
-  s.version     = '1.0.0.pre3'
-  s.date        = '2018-01-15'
+  s.version     = '1.0.0'
+  s.date        = '2018-01-17'
   s.summary     = "A Future class for simple process-based concurrency."
   s.description = <<-EOF
     SimpleFuture is class that simplifies coarse-grained concurrency using
@@ -15,8 +15,11 @@ Gem::Specification.new do |s|
 EOF
   s.authors     = ["Chris Reuter"]
   s.email       = 'chris@blit.ca'
+
+  # I'm just going to add everything so that if you've got the gem,
+  # you've also got the source distribution.  Yay! Open source!
   s.files       = ["README.md", "LICENSE.txt", "simple-future.gemspec",
-                   "Rakefile"] +
+                   "Rakefile", ".yardopts"] +
                   Dir.glob('doc/**/*') +
                   Dir.glob('{spec,lib}/*.rb')
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: simple-future
 version: !ruby/object:Gem::Version
-  version: 1.0.0.pre3
+  version: 1.0.0
 platform: ruby
 authors:
 - Chris Reuter
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-01-15 00:00:00.000000000 Z
+date: 2018-01-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -63,6 +63,7 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".yardopts"
 - LICENSE.txt
 - README.md
 - Rakefile
@@ -103,13 +104,13 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: 2.2.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">"
+  - - ">="
     - !ruby/object:Gem::Version
-      version: 1.3.1
+      version: '0'
 requirements:
 - A version of Ruby that implements Process.fork
 rubyforge_project: 
-rubygems_version: 2.6.14
+rubygems_version: 2.5.1
 signing_key: 
 specification_version: 4
 summary: A Future class for simple process-based concurrency.