diff-lcs 1.5.1 → 2.0.0

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,166 @@
+# Contributor Covenant 3.0 Code of Conduct
+
+## Our Pledge
+
+We pledge to make our community welcoming, safe, and equitable for all.
+
+We are committed to fostering an environment that respects and promotes the
+dignity, rights, and contributions of all individuals, regardless of
+characteristics including race, ethnicity, caste, color, age, physical
+characteristics, neurodiversity, disability, sex or gender, gender identity or
+expression, sexual orientation, language, philosophy or religion, national or
+social origin, socio-economic position, level of education, or other status. The
+same privileges of participation are extended to everyone who participates in
+good faith and in accordance with this Covenant.
+
+## Encouraged Behaviors
+
+While acknowledging differences in social norms, we all strive to meet our
+community's expectations for positive behavior. We also understand that our
+words and actions may be interpreted differently than we intend based on
+culture, background, or native language.
+
+With these considerations in mind, we agree to behave mindfully toward each
+other and act in ways that center our shared values, including:
+
+1. Respecting the **purpose of our community**, our activities, and our ways of
+   gathering.
+2. Engaging **kindly and honestly** with others.
+3. Respecting **different viewpoints** and experiences.
+4. **Taking responsibility** for our actions and contributions.
+5. Gracefully giving and accepting **constructive feedback**.
+6. Committing to **repairing harm** when it occurs.
+7. Behaving in other ways that promote and sustain the **well-being of our
+   community**.
+
+## Restricted Behaviors
+
+We agree to restrict the following behaviors in our community. Instances,
+threats, and promotion of these behaviors are violations of this Code of
+Conduct.
+
+1. **Harassment.** Violating explicitly expressed boundaries or engaging in
+   unnecessary personal attention after any clear request to stop.
+2. **Character attacks.** Making insulting, demeaning, or pejorative comments
+   directed at a community member or group of people.
+3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
+   behavior on the basis of immutable identities or traits.
+4. **Sexualization.** Behaving in a way that would generally be considered
+   inappropriately intimate in the context or purpose of the community.
+5. **Violating confidentiality**. Sharing or acting on someone's personal or
+   private information without their permission.
+6. **Endangerment.** Causing, encouraging, or threatening violence or other harm
+   toward any person or group.
+7. Behaving in other ways that **threaten the well-being** of our community.
+
+### Other Restrictions
+
+1. **Misleading identity.** Impersonating someone else for any reason, or
+   pretending to be someone else to evade enforcement actions.
+2. **Failing to credit sources.** Not properly crediting the sources of content
+   you contribute.
+3. **Promotional materials**. Sharing marketing or other commercial content in a
+   way that is outside the norms of the community.
+4. **Irresponsible communication.** Failing to responsibly present content which
+   includes, links or describes any other restricted behaviors.
+
+## Reporting an Issue
+
+Tensions can occur between community members even when they are trying their
+best to collaborate. Not every conflict represents a code of conduct violation,
+and this Code of Conduct reinforces encouraged behaviors and norms that can help
+avoid conflicts and minimize harm.
+
+When an incident does occur, it is important to report it promptly. To report a
+possible violation, create a [private security advisory][advisory] — violations
+of this code of conduct are considered security vulnerabilities.
+
+Community Moderators take reports of violations seriously and will make every
+effort to respond in a timely manner. They will investigate all reports of code
+of conduct violations, reviewing messages, logs, and recordings, or interviewing
+witnesses and other participants. Community Moderators will keep investigation
+and enforcement actions as transparent as possible while prioritizing safety and
+confidentiality. In order to honor these values, enforcement actions are carried
+out in private with the involved parties, but communicating to the whole
+community may be part of a mutually agreed upon resolution.
+
+## Addressing and Repairing Harm
+
+If an investigation by the Community Moderators finds that this Code of Conduct
+has been violated, the following enforcement ladder may be used to determine how
+best to repair harm, based on the incident's impact on the individuals involved
+and the community as a whole. Depending on the severity of a violation, lower
+rungs on the ladder may be skipped.
+
+1. Warning
+   1. Event: A violation involving a single incident or series of incidents.
+   2. Consequence: A private, written warning from the Community Moderators.
+   3. Repair: Examples of repair include a private written apology,
+      acknowledgement of responsibility, and seeking clarification on
+      expectations.
+
+2. Temporarily Limited Activities
+   1. Event: A repeated incidence of a violation that previously resulted in a
+      warning, or the first incidence of a more serious violation.
+   2. Consequence: A private, written warning with a time-limited cooldown
+      period designed to underscore the seriousness of the situation and give
+      the community members involved time to process the incident. The cooldown
+      period may be limited to particular communication channels or interactions
+      with particular community members.
+   3. Repair: Examples of repair may include making an apology, using the
+      cooldown period to reflect on actions and impact, and being thoughtful
+      about re-entering community spaces after the period is over.
+
+3. Temporary Suspension
+   1. Event: A pattern of repeated violation which the Community Moderators have
+      tried to address with warnings, or a single serious violation.
+   2. Consequence: A private written warning with conditions for return from
+      suspension. In general, temporary suspensions give the person being
+      suspended time to reflect upon their behavior and possible corrective
+      actions.
+   3. Repair: Examples of repair include respecting the spirit of the
+      suspension, meeting the specified conditions for return, and being
+      thoughtful about how to reintegrate with the community when the suspension
+      is lifted.
+
+4. Permanent Ban
+   1. Event: A pattern of repeated code of conduct violations that other steps
+      on the ladder have failed to resolve, or a violation so serious that the
+      Community Moderators determine there is no way to keep the community safe
+      with this person as a member.
+   2. Consequence: Access to all community spaces, tools, and communication
+      channels is removed. In general, permanent bans should be rarely used,
+      should have strong reasoning behind them, and should only be resorted to
+      if working through other remedies has failed to change the behavior.
+   3. Repair: There is no possible repair in cases of this severity.
+
+This enforcement ladder is intended as a guideline. It does not limit the
+ability of Community Managers to use their discretion and judgment, in keeping
+with the best interests of our community.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public or other
+spaces. Examples of representing our community include using an official email
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 3.0,
+permanently available at <https://www.contributor-covenant.org/version/3/0/>.
+
+Contributor Covenant is stewarded by the Organization for Ethical Source and
+licensed under CC BY-SA 4.0. To view a copy of this license, visit
+<https://creativecommons.org/licenses/by-sa/4.0/>.
+
+For answers to common questions about Contributor Covenant, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are provided at
+<https://www.contributor-covenant.org/translations>. Additional enforcement and
+community guideline resources can be found at
+<https://www.contributor-covenant.org/resources>. The enforcement ladder was
+inspired by the work of [Mozilla’s code of conduct team][inclusion].
+
+[advisory]: https://github.com/halostatue/diff-lcs/security/advisories/new
+[inclusion]: https://github.com/mozilla/inclusion

data/CONTRIBUTING.md

@@ -0,0 +1,127 @@
+# Contributing
+
+Contribution to diff-lcs is encouraged: bug reports, feature requests, or code
+contributions. New features should be proposed and discussed in an
+[issue][issues].
+
+Before contributing patches, please read the [Licence](./LICENCE.md).
+
+diff-lcs is governed under the [Contributor Covenant Code of Conduct][cccoc].
+
+## Code Guidelines
+
+I have several guidelines to contributing code through pull requests:
+
+- All code changes require tests. In most cases, this will be added or updated
+  unit tests. I use [Minitest][minitest].
+
+  - There are integration tests with RSpec which must not be broken, accessible
+    through `rake integration`. This requires a non-bundled RSpec,
+    `gem install rspec`.
+
+- I use code formatters, static analysis tools, and linting to ensure consistent
+  styles and formatting. There should be no warning output from test run
+  processes. I use [Standard Ruby][standardrb].
+
+- Proposed changes should be on a thoughtfully-named topic branch and organized
+  into logical commit chunks as appropriate.
+
+- Use [Conventional Commits][conventional] with my
+  [conventions](#commit-conventions).
+
+- Versions must not be updated in pull requests unless otherwise directed. This
+  means that you must not:
+
+  - Modify `VERSION` in `lib/diff/lcs/version.rb`. When your patch is accepted
+    and a release is made, the version will be updated at that point.
+
+  - Modify `diff-lcs.gemspec`; it is a generated file. (You _may_ use
+    `rake gemspec` to regenerate it if your change involves metadata related to
+    gem itself).
+
+  - Modify the `Gemfile`.
+
+- Documentation should be added or updated as appropriate for new or updated
+  functionality. The documentation is RDoc; diff-lcs does not use extensions
+  that may be present in alternative documentation generators.
+
+- All GitHub Actions checks marked as required must pass before a pull request
+  may be accepted and merged.
+
+- Add your name or GitHub handle to `CONTRIBUTORS.md` and a record in the
+  `CHANGELOG.md` as a separate commit from your main change. (Follow the style
+  in the `CHANGELOG.md` and provide a link to your PR.)
+
+- Include your DCO sign-off in each commit message (see [LICENCE](LICENCE.md)).
+
+## AI Contribution Policy
+
+diff-lcs is a library with complex interactions and subtle decisions (some of
+them possibly even wrong). It is extremely important that contributions of any
+sort be well understood by the submitter and that the developer can attest to
+the [Developer Certificate of Origin][dco] for each pull request (see
+[LICENCE](LICENCE.md)).
+
+Any contribution (bug, feature request, or pull request) that uses undeclared AI
+output will be rejected.
+
+## Test Dependencies
+
+diff-lcs uses Ryan Davis's [Hoe][Hoe] to manage the release process, and it adds
+a number of rake tasks. You will mostly be interested in `rake`, which runs
+tests in the same way that `rake spec` does.
+
+To assist with the installation of the development dependencies for diff-lcs, I
+have provided a Gemfile pointing to the (generated) `diff-lcs.gemspec` file.
+This will permit you to use `bundle install` to install the dependencies.
+
+You can run tests with code coverage analysis by running `rake spec:coverage`.
+
+## Commit Conventions
+
+diff-lcs has adopted a variation of the Conventional Commits format for commit
+messages. The following types are permitted:
+
+| Type    | Purpose                                               |
+| ------- | ----------------------------------------------------- |
+| `feat`  | A new feature                                         |
+| `fix`   | A bug fix                                             |
+| `chore` | A code change that is neither a bug fix nor a feature |
+| `docs`  | Documentation updates                                 |
+| `deps`  | Dependency updates, including GitHub Actions.         |
+
+I encourage the use of [Tim Pope's][tpope-qcm] or [Chris Beam's][cbeams]
+guidelines on the writing of commit messages
+
+I require the use of [git][trailers1] [trailers][trailers2] for specific
+additional metadata and strongly encourage it for others. The conditionally
+required metadata trailers are:
+
+- `Breaking-Change`: if the change is a breaking change. **Do not** use the
+  shorthand form (`feat!(scope)`) or `BREAKING CHANGE`.
+
+- `Signed-off-by`: this is required for all developers except me, as outlined in
+  the [Licence](./LICENCE.md#developer-certificate-of-origin).
+
+- `Fixes` or `Resolves`: If a change fixes one or more open [issues][issues],
+  that issue must be included in the `Fixes` or `Resolves` trailer. Multiple
+  issues should be listed comma separated in the same trailer:
+  `Fixes: #1, #5, #7`, but _may_ appear in separate trailers. While both `Fixes`
+  and `Resolves` are synonyms, only _one_ should be used in a given commit or
+  pull request.
+
+- `Related to`: If a change does not fix an issue, those issue references should
+  be included in this trailer.
+
+[cbeams]: https://cbea.ms/git-commit/
+[cccoc]: ./CODE_OF_CONDUCT.md
+[conventional]: https://www.conventionalcommits.org/en/v1.0.0/
+[dco]: licences/dco.txt
+[hoe]: https://github.com/seattlerb/hoe
+[issues]: https://github.com/halostatue/diff-lcs/issues
+[minitest]: https://github.com/seattlerb/minitest
+[rspec]: https://rspec.info/documentation/
+[standardrb]: https://github.com/standardrb/standard
+[tpope-qcm]: https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[trailers1]: https://git-scm.com/docs/git-interpret-trailers
+[trailers2]: https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---trailerlttokengtltvaluegt

data/CONTRIBUTORS.md

@@ -0,0 +1,59 @@
+# Contributors
+
+- Austin Ziegler ([@halostatue][gh-user-halostatue]) created diff-lcs.
+
+Thanks to everyone else who has contributed to diff-lcs over the years:
+
+- [@ginriki][gh-user-ginriki]
+- [@joshbronson][gh-user-joshbronson]
+- [@kevinmook][gh-user-kevinmook]
+- [@mckaz][gh-user-mckaz]
+- Akinori Musha
+- Artem Ignatyev
+- Brandon Fish
+- Baptiste Courtois ([@annih][gh-user-annih])
+- Camille Drapier
+- Cédric Boutillier
+- [@earlopain][gh-user-earlopain]
+- Gregg Kellogg
+- Jagdeep Singh
+- Jason Gladish
+- Jon Rowe
+- Josef Strzibny
+- Josep ([@apuratepp][gh-user-apuratepp])
+- Josh Bronson
+- Jun Aruga
+- Justin Steele
+- Kenichi Kamiya
+- Kensuke Nagae
+- Kevin Ansfield
+- Koichi Ito
+- Mark Friedgan
+- Masato Nakamura
+- Mark Young
+- Michael Granger
+- Myron Marston
+- Nicolas Leger
+- Oleg Orlov
+- Patrick Linnane
+- Paul Kunysch
+- Pete Higgins
+- Peter Goldstein
+- Peter Wagenet
+- Philippe Lafoucrière
+- Ryan Lovelett
+- Scott Steele
+- Simon Courtois
+- Tien ([@tiendo1011][gh-user-tiendo1011])
+- Tomas Jura
+- Vít Ondruch
+
+[gh-user-halostatue]: https://github.com/halostatue
+[gh-user-ginriki]: https://github.com/ginriki
+[gh-user-joshbronson]: https://github.com/joshbronson
+[gh-user-kevinmook]: https://github.com/kevinmook
+[gh-user-mckaz]: https://github.com/mckaz
+[gh-user-annih]: https://github.com/annih
+[gh-user-earlopain]: https://github.com/earlopain
+[gh-user-apuratepp]: https://github.com/apuratepp
+[gh-user-tiendo1011]: https://github.com/tiendo1011

data/LICENCE.md

@@ -0,0 +1,68 @@
+# Licence
+
+- SPDX-License-Identifier: [MIT][mit] OR [GPL-2.0-or-later][gpl2-or-later] OR
+  [Artistic-1.0-Perl][artistic-perl]
+
+This software is available under three disjunctive licences: the GNU GPL version
+2 (or at your option, a later version), the Perl Artistic license, or the MIT
+license. Note that my preference for licensing is the MIT license, but
+Algorithm::Diff was dually originally licensed with the Perl Artistic and the
+GNU GPL ("the same terms as Perl itself") and given that the Ruby implementation
+originally hewed pretty closely to the Perl version, I must maintain the
+additional licensing terms.
+
+- Copyright 2004-2026 Austin Ziegler and contributors.
+- Adapted from Algorithm::Diff (Perl) by Ned Konz and a Smalltalk version by
+  Mario I. Wolczko.
+
+## MIT License
+
+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.
+
+## Perl Artistic License
+
+See [licences/artistic.txt](licences/artistic.txt) in the main distribution.
+
+## GNU GPL version 2
+
+See the file [licences/COPYING.txt](licences/COPYING.txt) in the main
+distribution.
+
+## Developer Certificate of Origin
+
+All contributors **must** certify they are willing and able to provide their
+contributions under the terms of _all_ of this project's licences with the
+certification of the [Developer Certificate of Origin (Version 1.1)][dco].
+
+Such certification is provided by ensuring that a `Signed-off-by`
+[commit trailer][trailer] is present on every commit:
+
+    Signed-off-by: FirstName LastName <email@example.org>
+
+The `Signed-off-by` trailer can be automatically added by git with the `-s` or
+`--signoff` option on `git commit`:
+
+```sh
+git commit --signoff
+```
+
+[artistic-perl]: https://spdx.org/licenses/Artistic-1.0-Perl.html
+[gpl2-or-later]: https://spdx.org/licenses/GPL-2.0-or-later.html
+[mit]: https://spdx.org/licenses/MIT.html
+[trailer]: https://git-scm.com/docs/git-interpret-trailers
+[dco]: licences/dco.txt

data/Manifest.txt

@@ -1,53 +1,35 @@
-.rspec
-Code-of-Conduct.md
-Contributing.md
-History.md
-License.md
+CHANGELOG.md
+CODE_OF_CONDUCT.md
+CONTRIBUTING.md
+CONTRIBUTORS.md
+LICENCE.md
 Manifest.txt
-README.rdoc
+README.md
 Rakefile
-bin/htmldiff
+SECURITY.md
 bin/ldiff
-docs/COPYING.txt
-docs/artistic.txt
+integration/compare/array_diff_spec.rb
+integration/compare/hash_diff_spec.rb
+integration/compare/string_diff_spec.rb
+integration/rspec_differ_spec.rb
+integration/rspec_expectations_spec.rb
+integration/runner
 lib/diff-lcs.rb
 lib/diff/lcs.rb
 lib/diff/lcs/array.rb
-lib/diff/lcs/backports.rb
 lib/diff/lcs/block.rb
 lib/diff/lcs/callbacks.rb
 lib/diff/lcs/change.rb
-lib/diff/lcs/htmldiff.rb
 lib/diff/lcs/hunk.rb
 lib/diff/lcs/internals.rb
 lib/diff/lcs/ldiff.rb
 lib/diff/lcs/string.rb
+lib/diff/lcs/version.rb
+licenses/COPYING.txt
+licenses/artistic.txt
+licenses/dco.txt
 spec/change_spec.rb
 spec/diff_spec.rb
-spec/fixtures/aX
-spec/fixtures/bXaX
-spec/fixtures/ds1.csv
-spec/fixtures/ds2.csv
-spec/fixtures/ldiff/output.diff
-spec/fixtures/ldiff/output.diff-c
-spec/fixtures/ldiff/output.diff-e
-spec/fixtures/ldiff/output.diff-f
-spec/fixtures/ldiff/output.diff-u
-spec/fixtures/ldiff/output.diff.chef
-spec/fixtures/ldiff/output.diff.chef-c
-spec/fixtures/ldiff/output.diff.chef-e
-spec/fixtures/ldiff/output.diff.chef-f
-spec/fixtures/ldiff/output.diff.chef-u
-spec/fixtures/ldiff/output.diff.chef2
-spec/fixtures/ldiff/output.diff.chef2-c
-spec/fixtures/ldiff/output.diff.chef2-d
-spec/fixtures/ldiff/output.diff.chef2-e
-spec/fixtures/ldiff/output.diff.chef2-f
-spec/fixtures/ldiff/output.diff.chef2-u
-spec/fixtures/new-chef
-spec/fixtures/new-chef2
-spec/fixtures/old-chef
-spec/fixtures/old-chef2
 spec/hunk_spec.rb
 spec/issues_spec.rb
 spec/lcs_spec.rb
@@ -57,3 +39,85 @@ spec/sdiff_spec.rb
 spec/spec_helper.rb
 spec/traverse_balanced_spec.rb
 spec/traverse_sequences_spec.rb
+test/fixtures/123_x
+test/fixtures/456_x
+test/fixtures/aX
+test/fixtures/bXaX
+test/fixtures/ds1.csv
+test/fixtures/ds2.csv
+test/fixtures/empty
+test/fixtures/file1.bin
+test/fixtures/file2.bin
+test/fixtures/four_lines
+test/fixtures/four_lines_with_missing_new_line
+test/fixtures/ldiff/diff.missing_new_line1-e
+test/fixtures/ldiff/diff.missing_new_line1-f
+test/fixtures/ldiff/diff.missing_new_line2-e
+test/fixtures/ldiff/diff.missing_new_line2-f
+test/fixtures/ldiff/error.diff.chef-e
+test/fixtures/ldiff/error.diff.chef-f
+test/fixtures/ldiff/error.diff.missing_new_line1-e
+test/fixtures/ldiff/error.diff.missing_new_line1-f
+test/fixtures/ldiff/error.diff.missing_new_line2-e
+test/fixtures/ldiff/error.diff.missing_new_line2-f
+test/fixtures/ldiff/output.diff
+test/fixtures/ldiff/output.diff-c
+test/fixtures/ldiff/output.diff-u
+test/fixtures/ldiff/output.diff.bin1
+test/fixtures/ldiff/output.diff.bin1-c
+test/fixtures/ldiff/output.diff.bin1-e
+test/fixtures/ldiff/output.diff.bin1-f
+test/fixtures/ldiff/output.diff.bin1-u
+test/fixtures/ldiff/output.diff.bin2
+test/fixtures/ldiff/output.diff.bin2-c
+test/fixtures/ldiff/output.diff.bin2-e
+test/fixtures/ldiff/output.diff.bin2-f
+test/fixtures/ldiff/output.diff.bin2-u
+test/fixtures/ldiff/output.diff.chef
+test/fixtures/ldiff/output.diff.chef-c
+test/fixtures/ldiff/output.diff.chef-u
+test/fixtures/ldiff/output.diff.chef2
+test/fixtures/ldiff/output.diff.chef2-c
+test/fixtures/ldiff/output.diff.chef2-d
+test/fixtures/ldiff/output.diff.chef2-u
+test/fixtures/ldiff/output.diff.empty.vs.four_lines
+test/fixtures/ldiff/output.diff.empty.vs.four_lines-c
+test/fixtures/ldiff/output.diff.empty.vs.four_lines-e
+test/fixtures/ldiff/output.diff.empty.vs.four_lines-f
+test/fixtures/ldiff/output.diff.empty.vs.four_lines-u
+test/fixtures/ldiff/output.diff.four_lines.vs.empty
+test/fixtures/ldiff/output.diff.four_lines.vs.empty-c
+test/fixtures/ldiff/output.diff.four_lines.vs.empty-e
+test/fixtures/ldiff/output.diff.four_lines.vs.empty-f
+test/fixtures/ldiff/output.diff.four_lines.vs.empty-u
+test/fixtures/ldiff/output.diff.issue95_trailing_context
+test/fixtures/ldiff/output.diff.issue95_trailing_context-c
+test/fixtures/ldiff/output.diff.issue95_trailing_context-e
+test/fixtures/ldiff/output.diff.issue95_trailing_context-f
+test/fixtures/ldiff/output.diff.issue95_trailing_context-u
+test/fixtures/ldiff/output.diff.missing_new_line1
+test/fixtures/ldiff/output.diff.missing_new_line1-c
+test/fixtures/ldiff/output.diff.missing_new_line1-e
+test/fixtures/ldiff/output.diff.missing_new_line1-f
+test/fixtures/ldiff/output.diff.missing_new_line1-u
+test/fixtures/ldiff/output.diff.missing_new_line2
+test/fixtures/ldiff/output.diff.missing_new_line2-c
+test/fixtures/ldiff/output.diff.missing_new_line2-e
+test/fixtures/ldiff/output.diff.missing_new_line2-f
+test/fixtures/ldiff/output.diff.missing_new_line2-u
+test/fixtures/new-chef
+test/fixtures/new-chef2
+test/fixtures/old-chef
+test/fixtures/old-chef2
+test/test_block.rb
+test/test_change.rb
+test/test_diff.rb
+test/test_helper.rb
+test/test_hunk.rb
+test/test_issues.rb
+test/test_lcs.rb
+test/test_ldiff.rb
+test/test_patch.rb
+test/test_sdiff.rb
+test/test_traverse_balanced.rb
+test/test_traverse_sequences.rb

data/README.md

@@ -0,0 +1,105 @@
+# Diff::LCS
+
+[![RubyGems Version][shield-gems]][rubygems] ![Coveralls][shield-coveralls]
+[![Build Status][shield-ci]][ci-workflow]
+
+- code :: <https://github.com/halostatue/diff-lcs>
+- issues :: <https://github.com/halostatue/diff-lcs/issues>
+- docs :: <https://halostatue.github.io/diff-lcs/>
+- changelog :: <https://github.com/halostatue/diff-lcs/blob/main/CHANGELOG.md>
+
+## Description
+
+Diff::LCS computes the difference between two Enumerable sequences using the
+McIlroy-Hunt longest common subsequence (LCS) algorithm. It includes utilities
+to create a simple HTML diff output format and a standard diff-like tool.
+
+This is release 2.0, which has significant breaking changes (removal of
+deprecations and workarounds) and requires at least Ruby 3.2 or higher. See full
+details in the `CHANGELOG`, but users of diff-lcs should not notice any
+significant changes to the APIs.
+
+### Performance and Compatibility
+
+I have not run any benchmarks, but the use of immutable Data classes and the
+removal of a number of inner loop conditionals related to encoding and String
+handling (which have been unnecessary since at least Ruby 2.1 but kept for
+strict compatibility) should allow better optimization by modern Ruby
+implementations.
+
+If you are using RSpec for your test suite, you are unlikely to be able to use
+Diff::LCS 2.0 because of the minimum Ruby version unless the developers of RSpec
+loosen their version constraints. I cannot control this and have raised
+[rspec/rspec#290][rspec-issue-290].
+
+## Synopsis
+
+Using this module is quite simple. By default, Diff::LCS does not extend objects
+with the Diff::LCS interface, but will be called as if it were a function:
+
+```ruby
+require 'diff/lcs'
+
+seq1 = %w(a b c e h j l m n p)
+seq2 = %w(b c d e f j k l m r s t)
+
+lcs = Diff::LCS.LCS(seq1, seq2)
+diffs = Diff::LCS.diff(seq1, seq2)
+sdiff = Diff::LCS.sdiff(seq1, seq2)
+seq = Diff::LCS.traverse_sequences(seq1, seq2, callback_obj)
+bal = Diff::LCS.traverse_balanced(seq1, seq2, callback_obj)
+seq2 == Diff::LCS.patch!(seq1, diffs)
+seq1 == Diff::LCS.unpatch!(seq2, diffs)
+seq2 == Diff::LCS.patch!(seq1, sdiff)
+seq1 == Diff::LCS.unpatch!(seq2, sdiff)
+```
+
+Objects can be extended with Diff::LCS:
+
+```ruby
+seq1.extend(Diff::LCS)
+lcs = seq1.lcs(seq2)
+diffs = seq1.diff(seq2)
+sdiff = seq1.sdiff(seq2)
+seq = seq1.traverse_sequences(seq2, callback_obj)
+bal = seq1.traverse_balanced(seq2, callback_obj)
+seq2 == seq1.patch!(diffs)
+seq1 == seq2.unpatch!(diffs)
+seq2 == seq1.patch!(sdiff)
+seq1 == seq2.unpatch!(sdiff)
+```
+
+By requiring 'diff/lcs/array' or 'diff/lcs/string', Array or String will be
+extended for use this way.
+
+Note that Diff::LCS requires a sequenced enumerable container, which means that
+the order of enumeration is both predictable and consistent for the same set of
+data. While it is theoretically possible to generate a diff for an unordered
+hash, it will only be meaningful if the enumeration of the hashes is consistent.
+In general, this will mean that containers that behave like String or Array will
+perform best.
+
+## History
+
+Diff::LCS is a port of Perl's Algorithm::Diff that uses the McIlroy-Hunt longest
+common subsequence (LCS) algorithm to compute intelligent differences between
+two sequenced enumerable containers. The implementation is based on Mario I.
+Wolczko's [Smalltalk version 1.2][smalltalk] (1993) and Ned Konz's Perl version
+[Algorithm::Diff 1.15][perl]. `Diff::LCS#sdiff` and
+`Diff::LCS#traverse_balanced` were originally written for the Perl version by
+Mike Schilli.
+
+The algorithm is described in <em>A Fast Algorithm for Computing Longest Common
+Subsequences</em>, CACM, vol.20, no.5, pp.350-353, May 1977, with a few minor
+improvements to improve the speed. A simplified description of the algorithm,
+originally written for the Perl version, was written by Mark-Jason Dominus.
+
+[ci-workflow]: https://github.com/halostatue/diff-lcs/actions/workflows/ci.yml
+[coveralls]: https://coveralls.io/github/halostatue/diff-lcs?branch=main
+[perl]: https://search.cpan.org/~nedkonz/Algorithm-Diff-1.15/
+[rspec-issue-290]: https://github.com/rspec/rspec/issues/290
+[rubygems]: https://rubygems.org/gems/diff-lcs
+[shield-ci]: https://img.shields.io/github/actions/workflow/status/halostatue/diff-lcs/ci.yml?style=for-the-badge "Build Status"
+[shield-coveralls]: https://img.shields.io/coverallsCoverage/github/halostatue/diff-lcs?style=for-the-badge
+[shield-gems]: https://img.shields.io/gem/v/diff-lcs?style=for-the-badge "Version"
+[smalltalk]: ftp://st.cs.uiuc.edu/pub/Smalltalk/MANCHESTER/manchester/4.0/diff.st