Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
branch: master
Commits on May 6, 2015
  1. Merge pull request #18 from philipmw/rspec3

    authored
    rspec 3
  2. rspec 3

    Philip White authored
  3. Merge pull request #16 from philipmw/travis

    authored
    Travis CI support
  4. Travis CI support

    Philip White authored
  5. Merge pull request #17 from philipmw/bundler

    authored
    bundler works
  6. bundler works

    Philip White authored
Commits on Dec 23, 2014
  1. 0.3.1

    authored
Commits on Apr 24, 2014
  1. Merge pull request #12 from philipmw/support-marshalling

    authored
    Support marshalling a Promise
Commits on Apr 15, 2014
  1. @philipmw

    Support marshalling a Promise

    philipmw authored
Commits on Apr 14, 2014
  1. Merge pull request #11 from philipmw/respond-to-second-argument

    authored
    Support second argument to #respond_to?
  2. Merge pull request #10 from philipmw/fix-and-modernize-specs

    authored
    Fix and modernize specs
Commits on Apr 10, 2014
  1. @philipmw

    Support second argument to #respond_to?

    philipmw authored
    This matches Object's interface in Ruby 1.8.7--2.1.1 (at least), and avoids a
    warning that our #respond_to? "is old fashion which takes only one parameter".
  2. @philipmw

    Fix and modernize specs

    philipmw authored
    No change to functionality or test coverage, but specs now PASS and
    do not give any deprecation warnings.
Commits on Oct 12, 2012
  1. Merge pull request #5 from michaeljbishop/update-for-new-rspec

    authored
    Updated the test case, ensured test passage.
Commits on Oct 10, 2012
  1. @michaeljbishop

    Updated the test case, ensured test passage.

    michaeljbishop authored
    The test case needed to be updated for the latest RSpec version.
    The tests were failing because Future and Object didn't remove their
    methods if they inherited BasicObject. In that case, equal? wasn't
    overridden as well as the equality operators and any RSpec test that
    compared the promise result to another result using '==' would fail.
Commits on Jun 29, 2010
  1. Bump to version 0.2.1

    authored
  2. Update the AUTHORS file

    authored
Commits on Jun 23, 2010
  1. @bendiken

    Improved the YARD annotations.

    bendiken authored committed
    * YARD doesn't define an Any type, use Object instead.
    * YARD does define a Boolean pseudo-type which is (much) preferred to listing both true and false.
    * YARD @example blocks don't need Markdown indentation (2 spaces is sufficient, and convention).
  2. @bendiken

    Bumped the YARD dependency.

    bendiken authored committed
  3. @bendiken

    Fixed the Promise/Future constructors to correctly accept a block.

    bendiken authored committed
    Now it is possible to construct a promise directly by saying: Promise.new { 42 }
  4. @bendiken

    Simplified and fixed #method_missing for promises/futures.

    bendiken authored committed
    This fixes a potential bug wherein a promise result having a custom #send method would muck things up with regards to method call forwarding for promises/futures.
  5. @bendiken

    Optimized all equality comparisons involved in forcing promises/futures.

    bendiken authored committed
    This also fixes a potential bug wherein a promise result that redefined its #== operator to always return true would have really messed with the conditionals that we rely on for forcing promises/futures.
Commits on Jun 22, 2010
  1. Bump to version 0.2.0

    authored
Commits on Jun 19, 2010
  1. Update tests to check #eql? and #equal? one-way only, which works. Ruby

    authored
    implements #equal? at too low a level to make it go both ways.  #eql?
    defaults to #equal? but results that re-implement #eql? ought to work
    fine both ways.
  2. Make results an explicit holder object to prevent

    authored
    re-evaluation when the result is nil or false.  Hold errors to prevent
    re-evaluation if an exception is raised.
  3. Remove pending for equality tests; was not an RSpec problem but an or…

    authored
    …dering
    
    problem.  They are correctly fails.
Something went wrong with that request. Please try again.