etude_for_ruby 0.1.4 → 0.2.3

data/vendor/bundle/ruby/2.4.0/gems/rspec-expectations-3.5.0/LICENSE.md

@@ -1,25 +0,0 @@
-The MIT License (MIT)
-=====================
-
-* Copyright © 2012 David Chelimsky, Myron Marston
-* Copyright © 2006 David Chelimsky, The RSpec Development Team
-* Copyright © 2005 Steven Baker
-
-Permission is hereby granted, free of charge, to any person obtaining
-a copy of this software and associated documentation files (the
-"Software"), to deal in the Software without restriction, including
-without limitation the rights to use, copy, modify, merge, publish,
-distribute, sublicense, and/or sell copies of the Software, and to
-permit persons to whom the Software is furnished to do so, subject to
-the following conditions:
-
-The above copyright notice and this permission notice shall be
-included in all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
-IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
-CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
-TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
-SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/vendor/bundle/ruby/2.4.0/gems/rspec-expectations-3.5.0/README.md

@@ -1,303 +0,0 @@
-# RSpec Expectations [![Build Status](https://secure.travis-ci.org/rspec/rspec-expectations.svg?branch=master)](http://travis-ci.org/rspec/rspec-expectations) [![Code Climate](https://codeclimate.com/github/rspec/rspec-expectations.svg)](https://codeclimate.com/github/rspec/rspec-expectations)
-
-RSpec::Expectations lets you express expected outcomes on an object in an
-example.
-
-    expect(account.balance).to eq(Money.new(37.42, :USD))
-
-## Install
-
-If you want to use rspec-expectations with rspec, just install the rspec gem
-and RubyGems will also install rspec-expectations for you (along with
-rspec-core and rspec-mocks):
-
-    gem install rspec
-
-Want to run against the `master` branch? You'll need to include the dependent
-RSpec repos as well. Add the following to your `Gemfile`:
-
-```ruby
-%w[rspec-core rspec-expectations rspec-mocks rspec-support].each do |lib|
-  gem lib, :git => "git://github.com/rspec/#{lib}.git", :branch => 'master'
-end
-```
-
-If you want to use rspec-expectations with another tool, like Test::Unit,
-Minitest, or Cucumber, you can install it directly:
-
-    gem install rspec-expectations
-
-## Contributing
-
-Once you've set up the environment, you'll need to cd into the working
-directory of whichever repo you want to work in. From there you can run the
-specs and cucumber features, and make patches.
-
-NOTE: You do not need to use rspec-dev to work on a specific RSpec repo. You
-can treat each RSpec repo as an independent project.
-
-- [Build details](BUILD_DETAIL.md)
-- [Code of Conduct](CODE_OF_CONDUCT.md)
-- [Detailed contributing guide](CONTRIBUTING.md)
-- [Development setup guide](DEVELOPMENT.md)
-
-## Basic usage
-
-Here's an example using rspec-core:
-
-```ruby
-RSpec.describe Order do
-  it "sums the prices of the items in its line items" do
-    order = Order.new
-    order.add_entry(LineItem.new(:item => Item.new(
-      :price => Money.new(1.11, :USD)
-    )))
-    order.add_entry(LineItem.new(:item => Item.new(
-      :price => Money.new(2.22, :USD),
-      :quantity => 2
-    )))
-    expect(order.total).to eq(Money.new(5.55, :USD))
-  end
-end
-```
-
-The `describe` and `it` methods come from rspec-core.  The `Order`, `LineItem`, `Item` and `Money` classes would be from _your_ code. The last line of the example
-expresses an expected outcome. If `order.total == Money.new(5.55, :USD)`, then
-the example passes. If not, it fails with a message like:
-
-    expected: #<Money @value=5.55 @currency=:USD>
-         got: #<Money @value=1.11 @currency=:USD>
-
-## Built-in matchers
-
-### Equivalence
-
-```ruby
-expect(actual).to eq(expected)  # passes if actual == expected
-expect(actual).to eql(expected) # passes if actual.eql?(expected)
-expect(actual).not_to eql(not_expected) # passes if not(actual.eql?(expected))
-```
-
-Note: The new `expect` syntax no longer supports the `==` matcher.
-
-### Identity
-
-```ruby
-expect(actual).to be(expected)    # passes if actual.equal?(expected)
-expect(actual).to equal(expected) # passes if actual.equal?(expected)
-```
-
-### Comparisons
-
-```ruby
-expect(actual).to be >  expected
-expect(actual).to be >= expected
-expect(actual).to be <= expected
-expect(actual).to be <  expected
-expect(actual).to be_within(delta).of(expected)
-```
-
-### Regular expressions
-
-```ruby
-expect(actual).to match(/expression/)
-```
-
-Note: The new `expect` syntax no longer supports the `=~` matcher.
-
-### Types/classes
-
-```ruby
-expect(actual).to be_an_instance_of(expected) # passes if actual.class == expected
-expect(actual).to be_a(expected)              # passes if actual.kind_of?(expected)
-expect(actual).to be_an(expected)             # an alias for be_a
-expect(actual).to be_a_kind_of(expected)      # another alias
-```
-
-### Truthiness
-
-```ruby
-expect(actual).to be_truthy   # passes if actual is truthy (not nil or false)
-expect(actual).to be true     # passes if actual == true
-expect(actual).to be_falsy    # passes if actual is falsy (nil or false)
-expect(actual).to be false    # passes if actual == false
-expect(actual).to be_nil      # passes if actual is nil
-expect(actual).to_not be_nil  # passes if actual is not nil
-```
-
-### Expecting errors
-
-```ruby
-expect { ... }.to raise_error
-expect { ... }.to raise_error(ErrorClass)
-expect { ... }.to raise_error("message")
-expect { ... }.to raise_error(ErrorClass, "message")
-```
-
-### Expecting throws
-
-```ruby
-expect { ... }.to throw_symbol
-expect { ... }.to throw_symbol(:symbol)
-expect { ... }.to throw_symbol(:symbol, 'value')
-```
-
-### Yielding
-
-```ruby
-expect { |b| 5.tap(&b) }.to yield_control # passes regardless of yielded args
-
-expect { |b| yield_if_true(true, &b) }.to yield_with_no_args # passes only if no args are yielded
-
-expect { |b| 5.tap(&b) }.to yield_with_args(5)
-expect { |b| 5.tap(&b) }.to yield_with_args(Fixnum)
-expect { |b| "a string".tap(&b) }.to yield_with_args(/str/)
-
-expect { |b| [1, 2, 3].each(&b) }.to yield_successive_args(1, 2, 3)
-expect { |b| { :a => 1, :b => 2 }.each(&b) }.to yield_successive_args([:a, 1], [:b, 2])
-```
-
-### Predicate matchers
-
-```ruby
-expect(actual).to be_xxx         # passes if actual.xxx?
-expect(actual).to have_xxx(:arg) # passes if actual.has_xxx?(:arg)
-```
-
-### Ranges (Ruby >= 1.9 only)
-
-```ruby
-expect(1..10).to cover(3)
-```
-
-### Collection membership
-
-```ruby
-expect(actual).to include(expected)
-expect(actual).to start_with(expected)
-expect(actual).to end_with(expected)
-
-expect(actual).to contain_exactly(individual, items)
-# ...which is the same as:
-expect(actual).to match_array(expected_array)
-```
-
-#### Examples
-
-```ruby
-expect([1, 2, 3]).to include(1)
-expect([1, 2, 3]).to include(1, 2)
-expect([1, 2, 3]).to start_with(1)
-expect([1, 2, 3]).to start_with(1, 2)
-expect([1, 2, 3]).to end_with(3)
-expect([1, 2, 3]).to end_with(2, 3)
-expect({:a => 'b'}).to include(:a => 'b')
-expect("this string").to include("is str")
-expect("this string").to start_with("this")
-expect("this string").to end_with("ring")
-expect([1, 2, 3]).to contain_exactly(2, 3, 1)
-expect([1, 2, 3]).to match_array([3, 2, 1])
-```
-
-## `should` syntax
-
-In addition to the `expect` syntax, rspec-expectations continues to support the
-`should` syntax:
-
-```ruby
-actual.should eq expected
-actual.should be > 3
-[1, 2, 3].should_not include 4
-```
-
-See [detailed information on the `should` syntax and its usage.](https://github.com/rspec/rspec-expectations/blob/master/Should.md)
-
-## Compound Matcher Expressions
-
-You can also create compound matcher expressions using `and` or `or`:
-
-``` ruby
-expect(alphabet).to start_with("a").and end_with("z")
-expect(stoplight.color).to eq("red").or eq("green").or eq("yellow")
-```
-
-## Composing Matchers
-
-Many of the built-in matchers are designed to take matchers as
-arguments, to allow you to flexibly specify only the essential
-aspects of an object or data structure. In addition, all of the
-built-in matchers have one or more aliases that provide better
-phrasing for when they are used as arguments to another matcher.
-
-### Examples
-
-```ruby
-expect { k += 1.05 }.to change { k }.by( a_value_within(0.1).of(1.0) )
-
-expect { s = "barn" }.to change { s }
-  .from( a_string_matching(/foo/) )
-  .to( a_string_matching(/bar/) )
-
-expect(["barn", 2.45]).to contain_exactly(
-  a_value_within(0.1).of(2.5),
-  a_string_starting_with("bar")
-)
-
-expect(["barn", "food", 2.45]).to end_with(
-  a_string_matching("foo"),
-  a_value > 2
-)
-
-expect(["barn", 2.45]).to include( a_string_starting_with("bar") )
-
-expect(:a => "food", :b => "good").to include(:a => a_string_matching(/foo/))
-
-hash = {
-  :a => {
-    :b => ["foo", 5],
-    :c => { :d => 2.05 }
-  }
-}
-
-expect(hash).to match(
-  :a => {
-    :b => a_collection_containing_exactly(
-      a_string_starting_with("f"),
-      an_instance_of(Fixnum)
-    ),
-    :c => { :d => (a_value < 3) }
-  }
-)
-
-expect { |probe|
-  [1, 2, 3].each(&probe)
-}.to yield_successive_args( a_value < 2, 2, a_value > 2 )
-```
-
-## Usage outside rspec-core
-
-You always need to load `rspec/expectations` even if you only want to use one part of the library:
-
-```ruby
-require 'rspec/expectations'
-```
-
-Then simply include `RSpec::Matchers` in any class:
-
-```ruby
-class MyClass
-  include RSpec::Matchers
-
-  def do_something(arg)
-    expect(arg).to be > 0
-    # do other stuff
-  end
-end
-```
-
-## Also see
-
-* [https://github.com/rspec/rspec](https://github.com/rspec/rspec)
-* [https://github.com/rspec/rspec-core](https://github.com/rspec/rspec-core)
-* [https://github.com/rspec/rspec-mocks](https://github.com/rspec/rspec-mocks)
-* [https://github.com/rspec/rspec-rails](https://github.com/rspec/rspec-rails)

data/vendor/bundle/ruby/2.4.0/gems/rspec-expectations-3.5.0/lib/rspec/expectations.rb

@@ -1,81 +0,0 @@
-require 'rspec/support'
-RSpec::Support.require_rspec_support "caller_filter"
-RSpec::Support.require_rspec_support "warnings"
-RSpec::Support.require_rspec_support "object_formatter"
-
-require 'rspec/matchers'
-
-RSpec::Support.define_optimized_require_for_rspec(:expectations) { |f| require_relative(f) }
-
-%w[
-  expectation_target
-  configuration
-  fail_with
-  handler
-  version
-].each { |file| RSpec::Support.require_rspec_expectations(file) }
-
-module RSpec
-  # RSpec::Expectations provides a simple, readable API to express
-  # the expected outcomes in a code example. To express an expected
-  # outcome, wrap an object or block in `expect`, call `to` or `to_not`
-  # (aliased as `not_to`) and pass it a matcher object:
-  #
-  #     expect(order.total).to eq(Money.new(5.55, :USD))
-  #     expect(list).to include(user)
-  #     expect(message).not_to match(/foo/)
-  #     expect { do_something }.to raise_error
-  #
-  # The last form (the block form) is needed to match against ruby constructs
-  # that are not objects, but can only be observed when executing a block
-  # of code. This includes raising errors, throwing symbols, yielding,
-  # and changing values.
-  #
-  # When `expect(...).to` is invoked with a matcher, it turns around
-  # and calls `matcher.matches?(<object wrapped by expect>)`.  For example,
-  # in the expression:
-  #
-  #     expect(order.total).to eq(Money.new(5.55, :USD))
-  #
-  # ...`eq(Money.new(5.55, :USD))` returns a matcher object, and it results
-  # in the equivalent of `eq.matches?(order.total)`. If `matches?` returns
-  # `true`, the expectation is met and execution continues. If `false`, then
-  # the spec fails with the message returned by `eq.failure_message`.
-  #
-  # Given the expression:
-  #
-  #     expect(order.entries).not_to include(entry)
-  #
-  # ...the `not_to` method (also available as `to_not`) invokes the equivalent of
-  # `include.matches?(order.entries)`, but it interprets `false` as success, and
-  # `true` as a failure, using the message generated by
-  # `include.failure_message_when_negated`.
-  #
-  # rspec-expectations ships with a standard set of useful matchers, and writing
-  # your own matchers is quite simple.
-  #
-  # See [RSpec::Matchers](../RSpec/Matchers) for more information about the
-  # built-in matchers that ship with rspec-expectations, and how to write your
-  # own custom matchers.
-  module Expectations
-    # Exception raised when an expectation fails.
-    #
-    # @note We subclass Exception so that in a stub implementation if
-    # the user sets an expectation, it can't be caught in their
-    # code by a bare `rescue`.
-    # @api public
-    class ExpectationNotMetError < Exception
-    end
-
-    # Exception raised from `aggregate_failures` when multiple expectations fail.
-    #
-    # @note The constant is defined here but the extensive logic of this class
-    #   is lazily defined when `FailureAggregator` is autoloaded, since we do
-    #   not need to waste time defining that functionality unless
-    #   `aggregate_failures` is used.
-    class MultipleExpectationsNotMetError < ExpectationNotMetError
-    end
-
-    autoload :FailureAggregator, "rspec/expectations/failure_aggregator"
-  end
-end

data/vendor/bundle/ruby/2.4.0/gems/rspec-expectations-3.5.0/lib/rspec/expectations/configuration.rb

@@ -1,201 +0,0 @@
-RSpec::Support.require_rspec_expectations "syntax"
-
-module RSpec
-  module Expectations
-    # Provides configuration options for rspec-expectations.
-    # If you are using rspec-core, you can access this via a
-    # block passed to `RSpec::Core::Configuration#expect_with`.
-    # Otherwise, you can access it via RSpec::Expectations.configuration.
-    #
-    # @example
-    #   RSpec.configure do |rspec|
-    #     rspec.expect_with :rspec do |c|
-    #       # c is the config object
-    #     end
-    #   end
-    #
-    #   # or
-    #
-    #   RSpec::Expectations.configuration
-    class Configuration
-      # @private
-      FALSE_POSITIVE_BEHAVIOURS =
-        {
-          :warn    => lambda { |message| RSpec.warning message },
-          :raise   => lambda { |message| raise ArgumentError, message },
-          :nothing => lambda { |_| true },
-        }
-
-      def initialize
-        @on_potential_false_positives = :warn
-      end
-
-      # Configures the supported syntax.
-      # @param [Array<Symbol>, Symbol] values the syntaxes to enable
-      # @example
-      #   RSpec.configure do |rspec|
-      #     rspec.expect_with :rspec do |c|
-      #       c.syntax = :should
-      #       # or
-      #       c.syntax = :expect
-      #       # or
-      #       c.syntax = [:should, :expect]
-      #     end
-      #   end
-      def syntax=(values)
-        if Array(values).include?(:expect)
-          Expectations::Syntax.enable_expect
-        else
-          Expectations::Syntax.disable_expect
-        end
-
-        if Array(values).include?(:should)
-          Expectations::Syntax.enable_should
-        else
-          Expectations::Syntax.disable_should
-        end
-      end
-
-      # The list of configured syntaxes.
-      # @return [Array<Symbol>] the list of configured syntaxes.
-      # @example
-      #   unless RSpec::Matchers.configuration.syntax.include?(:expect)
-      #     raise "this RSpec extension gem requires the rspec-expectations `:expect` syntax"
-      #   end
-      def syntax
-        syntaxes = []
-        syntaxes << :should if Expectations::Syntax.should_enabled?
-        syntaxes << :expect if Expectations::Syntax.expect_enabled?
-        syntaxes
-      end
-
-      if ::RSpec.respond_to?(:configuration)
-        def color?
-          ::RSpec.configuration.color_enabled?
-        end
-      else
-        # Indicates whether or not diffs should be colored.
-        # Delegates to rspec-core's color option if rspec-core
-        # is loaded; otherwise you can set it here.
-        attr_writer :color
-
-        # Indicates whether or not diffs should be colored.
-        # Delegates to rspec-core's color option if rspec-core
-        # is loaded; otherwise you can set it here.
-        def color?
-          defined?(@color) && @color
-        end
-      end
-
-      # Adds `should` and `should_not` to the given classes
-      # or modules. This can be used to ensure `should` works
-      # properly on things like proxy objects (particular
-      # `Delegator`-subclassed objects on 1.8).
-      #
-      # @param [Array<Module>] modules the list of classes or modules
-      #   to add `should` and `should_not` to.
-      def add_should_and_should_not_to(*modules)
-        modules.each do |mod|
-          Expectations::Syntax.enable_should(mod)
-        end
-      end
-
-      # Sets or gets the backtrace formatter. The backtrace formatter should
-      # implement `#format_backtrace(Array<String>)`. This is used
-      # to format backtraces of errors handled by the `raise_error`
-      # matcher.
-      #
-      # If you are using rspec-core, rspec-core's backtrace formatting
-      # will be used (including respecting the presence or absence of
-      # the `--backtrace` option).
-      #
-      # @!attribute [rw] backtrace_formatter
-      attr_writer :backtrace_formatter
-      def backtrace_formatter
-        @backtrace_formatter ||= if defined?(::RSpec.configuration.backtrace_formatter)
-                                   ::RSpec.configuration.backtrace_formatter
-                                 else
-                                   NullBacktraceFormatter
-                                 end
-      end
-
-      # Sets if custom matcher descriptions and failure messages
-      # should include clauses from methods defined using `chain`.
-      # @param value [Boolean]
-      attr_writer :include_chain_clauses_in_custom_matcher_descriptions
-
-      # Indicates whether or not custom matcher descriptions and failure messages
-      # should include clauses from methods defined using `chain`. It is
-      # false by default for backwards compatibility.
-      def include_chain_clauses_in_custom_matcher_descriptions?
-        @include_chain_clauses_in_custom_matcher_descriptions ||= false
-      end
-
-      # @private
-      def reset_syntaxes_to_default
-        self.syntax = [:should, :expect]
-        RSpec::Expectations::Syntax.warn_about_should!
-      end
-
-      # @api private
-      # Null implementation of a backtrace formatter used by default
-      # when rspec-core is not loaded. Does no filtering.
-      NullBacktraceFormatter = Module.new do
-        def self.format_backtrace(backtrace)
-          backtrace
-        end
-      end
-
-      # Configures whether RSpec will warn about matcher use which will
-      # potentially cause false positives in tests.
-      #
-      # @param [Boolean] boolean
-      def warn_about_potential_false_positives=(boolean)
-        if boolean
-          self.on_potential_false_positives = :warn
-        elsif warn_about_potential_false_positives?
-          self.on_potential_false_positives = :nothing
-        else
-          # no-op, handler is something else
-        end
-      end
-      #
-      # Configures what RSpec will do about matcher use which will
-      # potentially cause false positives in tests.
-      #
-      # @param [Symbol] behavior can be set to :warn, :raise or :nothing
-      def on_potential_false_positives=(behavior)
-        unless FALSE_POSITIVE_BEHAVIOURS.key?(behavior)
-          raise ArgumentError, "Supported values are: #{FALSE_POSITIVE_BEHAVIOURS.keys}"
-        end
-        @on_potential_false_positives = behavior
-      end
-
-      # Indicates what RSpec will do about matcher use which will
-      # potentially cause false positives in tests, generally you want to
-      # avoid such scenarios so this defaults to `true`.
-      attr_reader :on_potential_false_positives
-
-      # Indicates whether RSpec will warn about matcher use which will
-      # potentially cause false positives in tests, generally you want to
-      # avoid such scenarios so this defaults to `true`.
-      def warn_about_potential_false_positives?
-        on_potential_false_positives == :warn
-      end
-
-      # @private
-      def false_positives_handler
-        FALSE_POSITIVE_BEHAVIOURS.fetch(@on_potential_false_positives)
-      end
-    end
-
-    # The configuration object.
-    # @return [RSpec::Expectations::Configuration] the configuration object
-    def self.configuration
-      @configuration ||= Configuration.new
-    end
-
-    # set default syntax
-    configuration.reset_syntaxes_to_default
-  end
-end