spkl.Diffs 1.2.1

Install-Package spkl.Diffs -Version 1.2.1
dotnet add package spkl.Diffs --version 1.2.1
<PackageReference Include="spkl.Diffs" Version="1.2.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add spkl.Diffs --version 1.2.1
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: spkl.Diffs, 1.2.1"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install spkl.Diffs as a Cake Addin
#addin nuget:?package=spkl.Diffs&version=1.2.1

// Install spkl.Diffs as a Cake Tool
#tool nuget:?package=spkl.Diffs&version=1.2.1
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Provides a .NET Standard and .NET Core implementation to the diff algorithm (shortest edit script) described by Eugene Myers in "An O(ND) Difference Algorithm and Its Variations". Unlike some other implementations, this one can compare sequences of any object type, using the standard Equals method or a custom IEqualityComparer.

This project uses Semantic Versioning (https://semver.org/).

  • .NETCoreApp 2.1

    • No dependencies.
  • .NETCoreApp 3.1

    • No dependencies.
  • .NETStandard 2.0

    • No dependencies.
  • net5.0

    • No dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on spkl.Diffs:

Package Downloads

Create VertiGIS Mobile apps for Android, iOS, and UWP. Extend your apps with custom components, operations and services.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.2.1 404 4/5/2021
1.2.0 135 3/21/2021
1.1.0 104 2/3/2021
1.0.1 123 1/31/2021
1.0.0 97 1/27/2021

This is a bugfix release fixing two critical issues:
- The VArray containing the endpoints of the furthest reaching paths was created too small, leading to an IndexOutOfRangeException in some cases.
- The result could contain items that indicate they exists on "ResultType.Both" sides, yet they contained two different values as AItem and BItem.