NumericParser 0.9.6

NumericParser

A simple library for flexible parsing numeric values stored in strings to decimal values with precision.

Handles different formats like "1,111.11" or "2.222,22".

NuGet package installation

You can download NumericParser from nuget.org as a NuGet package, or simply run the following command in the Package Manager Console:

NuGet\Install-Package NumericParser

Usage example

using NumericParser;

var oldValue = "1,234,567.8";
var newValue = oldValue.ParseDecimal();
Console.WriteLine($"Parsed value: {newValue}");

var oldValue1 = "1.234.567,8";
if (oldValue1.TryParseDecimal(out var parsed))
{
  Console.WriteLine($"Parsed value: {parsed}");
}

Additional settings

There are some additional settings that can be used to customize the parsing process. Currently, the following settings are available:

• DecimalParserSettings.PreferThousandsInAmbiguousCases - if set to true, the parser will prefer the thousands separator in ambiguous cases. For example, if the input is "1,234" or "1.234", the parser will treat it as 1234m (and not as 1.234m) if this setting is set to true. By default, this setting is set to false.

using NumericParser;

var settings = new DecimalParserSettings { PreferThousandsInAmbiguousCases = true };

var oldValue = "1,234";
var newValue = oldValue.ParseDecimal(settings);
Console.WriteLine($"Parsed value: {newValue}"); // Parsed value: 1234m

Exceptions

The TryParseDecimal method does not throw any exceptions. If the input value is not a valid decimal number, the method returns false and the out parameter is set to null.

The ParseDecimal method throws an exception if the input value cannot be parsed into a decimal number:

• In case of null input, the exception is of type ArgumentNullException and contains the message "Value cannot be null. (Parameter 'value')".
• In other cases, such as an empty string, unexpected characters, or overflow, the exception is of type FormatException and contains the message "Input string was not in a correct format.".

Examples

*Depends on additional settings.

Benchmarks

NumericParser's code is allocation-free, based on Span<char> under the hood.

BenchmarkDotNet v0.14.0, Windows 10 (10.0.19045.4894/22H2/2022Update)
Intel Core i7-10750H CPU 2.60GHz, 1 CPU, 12 logical and 6 physical cores
.NET SDK 8.0.400
  [Host]   : .NET 8.0.8 (8.0.824.36612), X64 RyuJIT AVX2
  ShortRun : .NET 8.0.8 (8.0.824.36612), X64 RyuJIT AVX2

Job=ShortRun  IterationCount=3  LaunchCount=1
WarmupCount=3

* Legends *
Input     : Value of the 'Input' parameter
Mean      : Arithmetic mean of all measurements
Error     : Half of 99.9% confidence interval
StdDev    : Standard deviation of all measurements
Allocated : Allocated memory per single operation (managed only, inclusive, 1KB = 1024B)
1 ns      : 1 Nanosecond (0.000000001 sec)

<details> <summary>Benchmark results for .NET Framework 4.8.1</summary>

BenchmarkDotNet v0.14.0, Windows 10 (10.0.19045.4780/22H2/2022Update)
Intel Core i7-10750H CPU 2.60GHz, 1 CPU, 12 logical and 6 physical cores
  [Host]   : .NET Framework 4.8.1 (4.8.9261.0), X64 RyuJIT VectorSize=256
  ShortRun : .NET Framework 4.8.1 (4.8.9261.0), X64 RyuJIT VectorSize=256

Job=ShortRun  IterationCount=3  LaunchCount=1
WarmupCount=3

</details>