sb_prime_table 0.1.0

data/vendor/bundle/ruby/2.4.0/gems/coderay-1.1.2/lib/coderay.rb

@@ -0,0 +1,284 @@
+# encoding: utf-8
+# Encoding.default_internal = 'UTF-8'
+
+# = CodeRay Library
+#
+# CodeRay is a Ruby library for syntax highlighting.
+#
+# I try to make CodeRay easy to use and intuitive, but at the same time fully
+# featured, complete, fast and efficient.
+# 
+# See README.
+# 
+# It consists mainly of
+# * the main engine: CodeRay (Scanners::Scanner, Tokens, Encoders::Encoder)
+# * the plugin system: PluginHost, Plugin
+# * the scanners in CodeRay::Scanners
+# * the encoders in CodeRay::Encoders
+# * the styles in CodeRay::Styles
+# 
+# Here's a fancy graphic to light up this gray docu:
+# 
+# http://cycnus.de/raindark/coderay/scheme.png
+# 
+# == Documentation
+#
+# See CodeRay, Encoders, Scanners, Tokens.
+#
+# == Usage
+#
+# Remember you need RubyGems to use CodeRay, unless you have it in your load
+# path. Run Ruby with -rubygems option if required.
+#
+# === Highlight Ruby code in a string as html
+# 
+#   require 'coderay'
+#   print CodeRay.scan('puts "Hello, world!"', :ruby).html
+#
+#   # prints something like this:
+#   puts <span class="s">&quot;Hello, world!&quot;</span>
+# 
+# 
+# === Highlight C code from a file in a html div
+# 
+#   require 'coderay'
+#   print CodeRay.scan(File.read('ruby.h'), :c).div
+#   print CodeRay.scan_file('ruby.h').html.div
+# 
+# You can include this div in your page. The used CSS styles can be printed with
+# 
+#   % coderay_stylesheet
+# 
+# === Highlight without typing too much
+# 
+# If you are one of the hasty (or lazy, or extremely curious) people, just run this file:
+# 
+#   % ruby -rubygems /path/to/coderay/coderay.rb > example.html
+# 
+# and look at the file it created in your browser.
+# 
+# = CodeRay Module
+#
+# The CodeRay module provides convenience methods for the engine.
+#
+# * The +lang+ and +format+ arguments select Scanner and Encoder to use. These are
+#   simply lower-case symbols, like <tt>:python</tt> or <tt>:html</tt>.
+# * All methods take an optional hash as last parameter, +options+, that is send to
+#   the Encoder / Scanner.
+# * Input and language are always sorted in this order: +code+, +lang+.
+#   (This is in alphabetical order, if you need a mnemonic ;)
+# 
+# You should be able to highlight everything you want just using these methods;
+# so there is no need to dive into CodeRay's deep class hierarchy.
+#
+# The examples in the demo directory demonstrate common cases using this interface.
+#  
+# = Basic Access Ways
+#
+# Read this to get a general view what CodeRay provides.
+# 
+# == Scanning
+# 
+# Scanning means analysing an input string, splitting it up into Tokens.
+# Each Token knows about what type it is: string, comment, class name, etc.
+#
+# Each +lang+ (language) has its own Scanner; for example, <tt>:ruby</tt> code is
+# handled by CodeRay::Scanners::Ruby.
+# 
+# CodeRay.scan:: Scan a string in a given language into Tokens.
+#                This is the most common method to use.
+# CodeRay.scan_file:: Scan a file and guess the language using FileType.
+# 
+# The Tokens object you get from these methods can encode itself; see Tokens.
+# 
+# == Encoding
+#
+# Encoding means compiling Tokens into an output. This can be colored HTML or
+# LaTeX, a textual statistic or just the number of non-whitespace tokens.
+# 
+# Each Encoder provides output in a specific +format+, so you select Encoders via
+# formats like <tt>:html</tt> or <tt>:statistic</tt>.
+# 
+# CodeRay.encode:: Scan and encode a string in a given language.
+# CodeRay.encode_tokens:: Encode the given tokens.
+# CodeRay.encode_file:: Scan a file, guess the language using FileType and encode it.
+#
+# == All-in-One Encoding
+#
+# CodeRay.encode:: Highlight a string with a given input and output format.
+#
+# == Instanciating
+#
+# You can use an Encoder instance to highlight multiple inputs. This way, the setup
+# for this Encoder must only be done once.
+#
+# CodeRay.encoder:: Create an Encoder instance with format and options.
+# CodeRay.scanner:: Create an Scanner instance for lang, with '' as default code.
+#
+# To make use of CodeRay.scanner, use CodeRay::Scanner::code=.
+#
+# The scanning methods provide more flexibility; we recommend to use these.
+# 
+# == Reusing Scanners and Encoders
+# 
+# If you want to re-use scanners and encoders (because that is faster), see
+# CodeRay::Duo for the most convenient (and recommended) interface.
+module CodeRay
+  
+  $CODERAY_DEBUG ||= false
+  
+  CODERAY_PATH = File.expand_path('../coderay', __FILE__)
+  
+  # Assuming the path is a subpath of lib/coderay/
+  def self.coderay_path *path
+    File.join CODERAY_PATH, *path
+  end
+  
+  autoload :VERSION, 'coderay/version'
+  
+  # helpers
+  autoload :FileType,    coderay_path('helpers', 'file_type')
+  
+  # Tokens
+  autoload :Tokens,      coderay_path('tokens')
+  autoload :TokensProxy, coderay_path('tokens_proxy')
+  autoload :TokenKinds,  coderay_path('token_kinds')
+  
+  # Plugin system
+  autoload :PluginHost,  coderay_path('helpers', 'plugin_host')
+  autoload :Plugin,      coderay_path('helpers', 'plugin')
+  
+  # Plugins
+  autoload :Scanners,    coderay_path('scanners')
+  autoload :Encoders,    coderay_path('encoders')
+  autoload :Styles,      coderay_path('styles')
+  
+  # convenience access and reusable Encoder/Scanner pair
+  autoload :Duo,         coderay_path('duo')
+  
+  class << self
+    
+    # Scans the given +code+ (a String) with the Scanner for +lang+.
+    #
+    # This is a simple way to use CodeRay. Example:
+    #  require 'coderay'
+    #  page = CodeRay.scan("puts 'Hello, world!'", :ruby).html
+    #
+    # See also demo/demo_simple.
+    def scan code, lang, options = {}, &block
+      CodeRay::TokensProxy.new code, lang, options, block
+    end
+    
+    # Scans +filename+ (a path to a code file) with the Scanner for +lang+.
+    #
+    # If +lang+ is :auto or omitted, the CodeRay::FileType module is used to
+    # determine it. If it cannot find out what type it is, it uses
+    # CodeRay::Scanners::Text.
+    #
+    # Calls CodeRay.scan.
+    #
+    # Example:
+    #  require 'coderay'
+    #  page = CodeRay.scan_file('some_c_code.c').html
+    def scan_file filename, lang = :auto, options = {}, &block
+      lang = CodeRay::FileType.fetch filename, :text, true if lang == :auto
+      code = File.read filename
+      scan code, lang, options, &block
+    end
+    
+    # Encode a string.
+    #
+    # This scans +code+ with the the Scanner for +lang+ and then
+    # encodes it with the Encoder for +format+.
+    # +options+ will be passed to the Encoder.
+    #
+    # See CodeRay::Encoder.encode.
+    def encode code, lang, format, options = {}
+      encoder(format, options).encode code, lang, options
+    end
+    
+    # Encode pre-scanned Tokens.
+    # Use this together with CodeRay.scan:
+    #
+    #  require 'coderay'
+    #  
+    #  # Highlight a short Ruby code example in a HTML span
+    #  tokens = CodeRay.scan '1 + 2', :ruby
+    #  puts CodeRay.encode_tokens(tokens, :span)
+    #
+    def encode_tokens tokens, format, options = {}
+      encoder(format, options).encode_tokens tokens, options
+    end
+    
+    # Encodes +filename+ (a path to a code file) with the Scanner for +lang+.
+    #
+    # See CodeRay.scan_file.
+    # Notice that the second argument is the output +format+, not the input language.
+    #
+    # Example:
+    #  require 'coderay'
+    #  page = CodeRay.encode_file 'some_c_code.c', :html
+    def encode_file filename, format, options = {}
+      tokens = scan_file filename, :auto, get_scanner_options(options)
+      encode_tokens tokens, format, options
+    end
+    
+    # Highlight a string into a HTML <div>.
+    #
+    # CSS styles use classes, so you have to include a stylesheet
+    # in your output.
+    #
+    # See encode.
+    def highlight code, lang, options = { :css => :class }, format = :div
+      encode code, lang, format, options
+    end
+    
+    # Highlight a file into a HTML <div>.
+    #
+    # CSS styles use classes, so you have to include a stylesheet
+    # in your output.
+    #
+    # See encode.
+    def highlight_file filename, options = { :css => :class }, format = :div
+      encode_file filename, format, options
+    end
+    
+    # Finds the Encoder class for +format+ and creates an instance, passing
+    # +options+ to it.
+    #
+    # Example:
+    #  require 'coderay'
+    #  
+    #  stats = CodeRay.encoder(:statistic)
+    #  stats.encode("puts 17 + 4\n", :ruby)
+    #  
+    #  puts '%d out of %d tokens have the kind :integer.' % [
+    #    stats.type_stats[:integer].count,
+    #    stats.real_token_count
+    #  ]
+    #  #-> 2 out of 4 tokens have the kind :integer.
+    def encoder format, options = {}
+      CodeRay::Encoders[format].new options
+    end
+    
+    # Finds the Scanner class for +lang+ and creates an instance, passing
+    # +options+ to it.
+    #
+    # See Scanner.new.
+    def scanner lang, options = {}, &block
+      CodeRay::Scanners[lang].new '', options, &block
+    end
+    
+    # Extract the options for the scanner from the +options+ hash.
+    #
+    # Returns an empty Hash if <tt>:scanner_options</tt> is not set.
+    #
+    # This is used if a method like CodeRay.encode has to provide options
+    # for Encoder _and_ scanner.
+    def get_scanner_options options
+      options.fetch :scanner_options, {}
+    end
+    
+  end
+  
+end

data/vendor/bundle/ruby/2.4.0/gems/diff-lcs-1.3/.rspec

@@ -0,0 +1 @@
+--colour

data/vendor/bundle/ruby/2.4.0/gems/diff-lcs-1.3/Code-of-Conduct.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [INSERT EMAIL ADDRESS]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

data/vendor/bundle/ruby/2.4.0/gems/diff-lcs-1.3/Contributing.md

@@ -0,0 +1,83 @@
+## Contributing
+
+I value any contribution to Diff::LCS you can provide: a bug report, a feature
+request, or code contributions. Code contributions to Diff::LCS are especially
+<del>welcome</del>encouraged. Because Diff::LCS is a complex codebase, there
+are a few guidelines:
+
+*   Code changes *will not* be accepted without tests. The test suite is
+    written with [RSpec][].
+*   Match my coding style.
+*   Use a thoughtfully-named topic branch that contains your change. Rebase
+    your commits into logical chunks as necessary.
+*   Use [quality commit messages][].
+*   Do not change the version number; when your patch is accepted and a release
+    is made, the version will be updated at that point.
+*   Submit a GitHub pull request with your changes.
+*   New or changed behaviours require appropriate documentation.
+
+### Test Dependencies
+
+Diff::LCS uses Ryan Davis’s [Hoe][] to manage the release process, and it adds
+a number of rake tasks. You will mostly be interested in:
+
+    $ rake
+
+which runs the tests the same way that:
+
+    $ rake spec
+    $ rake travis
+
+will do.
+
+To assist with the installation of the development dependencies, I have
+provided a Gemfile pointing to the (generated) `diff-lcs.gemspec` file. This
+will permit you to do:
+
+    $ bundle install
+
+to get the development dependencies. If you aleady have `hoe` installed, you
+can accomplish the same thing with:
+
+    $ rake newb
+
+This task will install any missing dependencies, run the tests/specs, and
+generate the RDoc.
+
+You can run tests with code coverage analysis by running:
+
+    $ rake spec:coverage
+
+### Workflow
+
+Here's the most direct way to get your work merged into the project:
+
+*   Fork the project.
+*   Clone down your fork (`git clone git://github.com/<username>/diff-lcs.git`).
+*   Create a topic branch to contain your change (`git checkout -b
+    my_awesome_feature`).
+*   Hack away, add tests. Not necessarily in that order.
+*   Make sure everything still passes by running `rake`.
+*   If necessary, rebase your commits into logical chunks, without errors.
+*   Push the branch up (`git push origin my_awesome_feature`).
+*   Create a pull request against halostatue/diff-lcs and describe what your
+    change does and the why you think it should be merged.
+
+### Contributors
+
+*   Austin Ziegler created Diff::LCS.
+
+Thanks to everyone else who has contributed to Diff::LCS:
+
+*   Kenichi Kamiya
+*   Michael Granger
+*   Vít Ondruch
+*   Jon Rowe
+*   Koichi Ito
+*   Josef Strzibny
+*   Josh Bronson
+*   Mark Friedgan
+
+[Rspec]: http://rspec.info/documentation/
+[quality commit messages]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[Hoe]: https://github.com/seattlerb/hoe

data/vendor/bundle/ruby/2.4.0/gems/diff-lcs-1.3/History.md

@@ -0,0 +1,220 @@
+## 1.3 / 2017-01-18
+
+*   Bugs fixed:
+
+    *   Fixed an error for bin/ldiff --version. Fixes [issue #21][].
+    *   Force Diff::LCS::Change and Diff::LCS::ContextChange to only perform
+        equality comparisons against themselves. Provided by Kevin Mook in
+        [pull request #29][].
+    *   Fix tab expansion in htmldiff, provided by Mark Friedgan in
+        [pull request #25][].
+    *   Silence Ruby 2.4 Fixnum deprecation warnings. Fixxues [issue #38][] and
+        [pull request#36][].
+    *   Ensure that test dependencies are loaded properly. Fixes [issue #33][]
+        and [pull request #34][].
+    *   Fix [issue #1][] with incorrect intuition of patch direction. Tentative
+        fix, but the previous failure cases pass now.
+
+*   Tooling changes:
+
+    *   Added SimpleCov and Coveralls support.
+    *   Change the homepage (temporarily) to the GitHub repo.
+    *   Updated testing and gem infrastructure.
+    *   Modernized the specs.
+
+*   Cleaned up documentation.
+
+*   Added a Code of Conduct.
+
+## 1.2.5 / 2013-11-08
+
+*   Bugs fixed:
+
+    *   Comparing arrays flattened them too far, especially with
+        Diff::LCS.sdiff. Fixed by Josh Bronson in [pull request #23][].
+
+## 1.2.4 / 2013-04-20
+
+*   Bugs fixed:
+
+    *   A bug was introduced after 1.1.3 when pruning common sequences at the
+        start of comparison. Paul Kunysch (@pck) fixed this in
+        [pull request #18][]. Thanks!
+
+    *   The Rubinius (1.9 mode) bug in [rubinius/rubinius#2268][] has been
+        fixed by the Rubinius team two days after it was filed. Thanks for
+        fixing this so quickly!
+
+*   Switching to Raggi's hoe-gemspec2 for gemspec generation.
+
+## 1.2.3 / 2013-04-11
+
+*   Bugs Fixed:
+
+    *   The new encoding detection for diff output generation (added in 1.2.2)
+        introduced a bug if the left side of the comparison was the empty set.
+        Originally found in [rspec/rspec-expectations#238][] and
+        [rspec/rspec-expectations#239][]. Jon Rowe developed a reasonable
+        heuristic (left side, right side, empty string literal) to avoid this
+        bug.
+    *   There is a known issue with Rubinius in 1.9 mode reported in
+        [rubinius/rubinius#2268][] and demonstrated in the Travis CI builds.
+        For all other tested platforms, diff-lcs is considered stable. As soon
+        as a suitably small test-case can be created for the Rubinius team to
+        examine, this will be added to the Rubinius issue around this.
+
+## 1.2.2 / 2013-03-30
+
+*   Bugs Fixed:
+
+    *   Diff::LCS::Hunk could not properly generate a difference for comparison
+        sets that are not US-ASCII-compatible because of the use of literal
+        regular expressions and strings. Jon Rowe found this in
+        [rspec/rspec-expectations#219][] and provided a first pass
+        implementation in [pull request #15][]. I've reworked it because of
+        test failures in Rubinius when running in Ruby 1.9 mode. This coerces
+        the added values to the encoding of the old dataset (as determined by
+        the first piece of the old dataset).
+    *   Adding Travis CI testing for Ruby 2.0.
+
+## 1.2.1 / 2013-02-09
+
+*   Bugs Fixed:
+
+    *   As seen in [rspec/rspec-expectations#200][], the release of
+        Diff::LCS 1.2 introduced an unnecessary public API change to
+        Diff::LCS::Hunk (see the change at
+        [rspec/rspec-expectations@3d6fc82c][] for details). The new method name
+        (and behaviour) is more correct, but I should not have renamed the
+        function or should have at least provided an alias. This release
+        restores Diff::LCS::Hunk#unshift as an alias to #merge. Note that the
+        old #unshift behaviour was incorrect and will not be restored.
+
+## 1.2.0 / 2013-01-21
+
+*   Minor Enhancements:
+
+    *   Added special case handling for Diff::LCS.patch so that it handles
+        patches that are empty or contain no changes.
+    *   Added two new methods (#patch\_me and #unpatch\_me) to the includable
+        module.
+
+*   Bugs Fixed:
+
+    *   Fixed [issue #1][] patch direction detection.
+    *   Resolved [issue #2][] by handling `string[string.size, 1]` properly (it
+        returns `""` not `nil`).
+    *   Michael Granger (ged) fixed an implementation error in
+        Diff::LCS::Change and added specs in [pull request #8][]. Thanks!
+    *   Made the code auto-testable.
+    *   Vít Ondruch (voxik) provided the latest version of the GPL2 license
+        file in [pull request #10][]. Thanks!
+    *   Fixed a documentation issue with the includable versions of #patch! and
+        #unpatch! where they implied that they would replace the original
+        value. Given that Diff::LCS.patch always returns a copy, the
+        documentation was incorrect and has been corrected. To provide the
+        behaviour that was originally documented, two new methods were added to
+        provide this behaviour. Found by scooter-dangle in [issue #12][].
+        Thanks!
+
+*   Code Style Changes:
+
+    *   Removed trailing spaces.
+    *   Calling class methods using `.` instead of `::`.
+    *   Vít Ondruch (voxik) removed unnecessary shebangs in [pull request #9][].
+        Thanks!
+    *   Kenichi Kamiya (kachick) removed some warnings of an unused variable in
+        lucky [pull request #13][]. Thanks!
+    *   Embarked on a major refactoring to make the files a little more
+        manageable and understand the code on a deeper level.
+    *   Adding to http://travis-ci.org.
+
+## 1.1.3 / 2011-08-27
+
+*   Converted to 'hoe' for release.
+*   Converted tests to RSpec 2.
+*   Extracted the body of htmldiff into a class available from
+    diff/lcs/htmldiff.
+*   Migrated development and issue tracking to GitHub.
+*   Bugs fixed:
+
+    *   Eliminated the explicit use of RubyGems in both bin/htmldiff and
+        bin/ldiff. Resolves [issue #4][].
+    *   Eliminated Ruby warnings. Resolves [issue #3][].
+
+## 1.1.2 / 2004-10-20
+
+*   Fixed a problem reported by Mauricio Fernandez in htmldiff.
+
+## 1.1.1 / 2004-09-25
+
+*   Fixed bug #891 (Set returned from patch command does not contain last equal
+    part).
+*   Fixed a problem with callback initialisation code (it assumed that all
+    callbacks passed as classes can be initialised; now, it rescues
+    NoMethodError in the event of private :new being called).
+*   Modified the non-initialisable callbacks to have a private #new method.
+*   Moved ldiff core code to Diff::LCS::Ldiff (diff/lcs/ldiff.rb).
+
+## 1.1.0 / -
+
+*   Eliminated the need for Diff::LCS::Event and removed it.
+*   Added a contextual diff callback, Diff::LCS::ContextDiffCallback.
+*   Implemented patching/unpatching for standard Diff callback output formats
+    with both #diff and #sdiff.
+*   Extensive documentation changes.
+
+## 1.0.4
+
+*   Fixed a problem with bin/ldiff output, especially for unified format.
+    Newlines that should have been present weren't.
+*   Changed the .tar.gz installer to generate Windows batch files if ones do
+    not exist already. Removed the existing batch files as they didn't work.
+
+## 1.0.3
+
+*   Fixed a problem with #traverse\_sequences where the first difference from
+    the left sequence might not be appropriately captured.
+
+## 1.0.2
+
+*   Fixed an issue with ldiff not working because actions were changed from
+    symbols to strings.
+
+## 1.0.1
+
+*   Minor modifications to the gemspec, the README.
+*   Renamed the diff program to ldiff (as well as the companion batch file) so
+    as to not collide with the standard diff program.
+*   Fixed issues with RubyGems. Requires RubyGems > 0.6.1 or >= 0.6.1 with the
+    latest CVS version.
+
+## 1.0
+
+*   Initial release based mostly on Perl's Algorithm::Diff.
+
+[rubinius/rubinius#2268]: https://github.com/rubinius/rubinius/issues/2268
+[rspec/rspec-expectations#239]: https://github.com/rspec/rspec-expectations/issues/239
+[rspec/rspec-expectations#238]: https://github.com/rspec/rspec-expectations/issues/238
+[rspec/rspec-expectations#219]: https://github.com/rspec/rspec-expectations/issues/219
+[rspec/rspec-expectations@3d6fc82c]: https://github.com/rspec/rspec-expectations/commit/3d6fc82c
+[rspec/rspec-expectations#200]: https://github.com/rspec/rspec-expectations/pull/200
+[pull request #36]: https://github.com/halostatue/diff-lcs/pull/36
+[pull request #34]: https://github.com/halostatue/diff-lcs/pull/34
+[pull request #29]: https://github.com/halostatue/diff-lcs/pull/29
+[pull request #25]: https://github.com/halostatue/diff-lcs/pull/25
+[pull request #23]: https://github.com/halostatue/diff-lcs/pull/23
+[pull request #18]: https://github.com/halostatue/diff-lcs/pull/18
+[pull request #15]: https://github.com/halostatue/diff-lcs/pull/15
+[pull request #13]: https://github.com/halostatue/diff-lcs/pull/13
+[pull request #10]: https://github.com/halostatue/diff-lcs/pull/10
+[pull request #9]: https://github.com/halostatue/diff-lcs/pull/9
+[pull request #8]: https://github.com/halostatue/diff-lcs/pull/8
+[issue #38]: https://github.com/halostatue/diff-lcs/issues/38
+[issue #33]: https://github.com/halostatue/diff-lcs/issues/33
+[issue #21]: https://github.com/halostatue/diff-lcs/issues/21
+[issue #12]: https://github.com/halostatue/diff-lcs/issues/12
+[issue #4]: https://github.com/halostatue/diff-lcs/issues/4
+[issue #3]: https://github.com/halostatue/diff-lcs/issues/3
+[issue #2]: https://github.com/halostatue/diff-lcs/issues/2
+[issue #1]: https://github.com/halostatue/diff-lcs/issues/1