chore(deps): Bump NCalcSync from 6.4.0 to 7.1.0

[dependabot]

Updated NCalcSync from 6.4.0 to 7.1.0.

Release notes

Sourced from NCalcSync's releases.

7.1.0

What's Changed

• Refactor: Unify built-in function registration and evaluation by @​gumbarros in Refactor: Unify built-in function registration and evaluation ncalc/ncalc#610
• Add isNull and isNullOrEmpty built-in functions by @​gumbarros in Add isNull and isNullOrEmpty built-in functions ncalc/ncalc#612
• Added null coalescing operator by @​gumbarros in Added null coalescing operator ncalc/ncalc#613
• Fix: Honor StringComparer at in comparisons when NoStringTypeCoercion is set by @​cokert in Fix: Honor StringComparer at in comparisons when NoStringTypeCoercion is set ncalc/ncalc#614

NCalc docs re-design

With the help of Hallmark. Check it here: https://ncalc.github.io/ncalc

New Contributors

• @​cokert made their first contribution in Fix: Honor StringComparer at in comparisons when NoStringTypeCoercion is set ncalc/ncalc#614

Full Changelog: ncalc/ncalc@v7.0.2...v7.1.0

7.0.2

What's Changed

• Fix: Preserve dictionary comparers when copying ExpressionContext by @​gumbarros in Fix: Preserve dictionary comparers when copying ExpressionContext ncalc/ncalc#608

Full Changelog: ncalc/ncalc@v7.0.1...v7.0.2

7.0.1

What's Changed

• Added copy constructor to ExpressionContext.cs by @​gumbarros in Added copy constructor to ExpressionContext.cs ncalc/ncalc#607

Full Changelog: ncalc/ncalc@v7.0.0...v7.0.1

7.0.0

What's Changed

• Refactor expression configuration by separating immutable parsing/evaluation settings from runtime expression context by @​gumbarros in Split expression configuration from runtime parameters ncalc/ncalc#600
• Add ExpressionConfiguration, ExpressionEvaluationOptions for explicit configuration.
• Add FloatingPointNumberType and IntegerNumberType to configure parser number handling and string-to-number coercion in math helpers.
• Improve parser caching by including culture in the parser cache key.
• Refactor: Generate type-aware comparisons and optimize common numeric paths by @​gumbarros in Refactor: Generate type-aware comparisons and optimize common numeric paths ncalc/ncalc#601
• Fix serialization of floating-point numbers by @​gumbarros in Fix serialization of floating-point numbers ncalc/ncalc#605

Breaking Changes

• ExpressionContext now represents only per-evaluation runtime state. StaticParameters was renamed to Parameters, and Options, CultureInfo, MathHelperOptions, ComparisonOptions, and the implicit conversions from ExpressionOptions/CultureInfo were removed. Configure parsing and evaluation with ExpressionConfiguration instead.
• ExpressionContext is no longer a record and all props are init only to incentive immutability.
• Expression.Options no longer exposes the getter. It is kept only as a setter that replaces Expression.Configuration using ExpressionConfiguration.FromOptions(...). Use Expression.Configuration, Expression.ParserOptions, Expression.EvaluationOptions, Expression.CultureInfo, and Expression.Configuration.CacheEnabled.
• Expression constructors and IExpressionFactory.Create now accept ExpressionConfiguration and CultureInfo.
• Parameters, DynamicParameters, AsyncParameters, Functions, and AsyncFunctions on Expression no longer have setters. Mutate the dictionaries on Expression.Context or replace them through a new ExpressionContext.
• LogicalExpressionArgumentSeparator was renamed to ArgumentSeparator.
• LogicalExpressionParserOptions no longer exposes DecimalAsDefault and LongAsDefault. Use FloatingPointNumberType and IntegerNumberType.
• LogicalExpressionParser.GetOrCreateExpressionParser now requires a CultureInfo, and LogicalExpressionParser.Parse accepts culture separately from parser options.
• ILogicalExpressionFactory.Create now accepts LogicalExpressionParserOptions? and CultureInfo? instead of ExpressionOptions.
• IEvaluationVisitorFactory, EvaluationVisitor, and AsyncEvaluationVisitor now require ExpressionEvaluationOptions and CultureInfo.
• LogicalExpression extension methods Evaluate(...) and EvaluateAsync(...) were removed. Evaluate through Expression or instantiate the appropriate evaluation visitor.
• ComparisonOptions was removed. Use StringComparer property.
• MathHelperOptions was renamed to MathOptions.
• LogicalExpressionParserContext was renamed to LogicalExpressionParseContext following Parlot convention
• The NCalc.Antlr package/plugin was removed. Use the default Parlot parser or provide a custom ILogicalExpressionFactory.

Migration Guide: https://ncalc.github.io/ncalc/articles/project/migrate_v6_to_v7.html

Full Changelog: ncalc/ncalc@v6.4.0...v7.0.0

Commits viewable in compare view.

[tylerkron]

Rebased onto main and pushed the lock-file commit Dependabot cannot produce.

The red CI was never about NCalc. Each head's packages.lock.json records the shared library's full transitive closure, and Dependabot rewrites only the lock file in the directory whose manifest it edited — so this one-line csproj change invalidated six lock files and shipped one, and the locked-mode restore in Directory.Build.props failed the other heads with NU1004. .github/scripts/refresh_lock_files.sh regenerates all six.

This is a major version, so the behaviour was measured, not assumed

NCalc is reached from exactly one place — AbstractChannel.ScaleExpression — and nothing in the repo tests it. That path builds new Expression(s) { Parameters = { ["x"] = 1 } }, calls Evaluate() once as a validity probe, then re-evaluates per sample and Convert.ToDouble()s the result.

A standalone probe replaying that exact sequence under 6.4.0 and 7.1.0 over 27 expressions produced byte-identical output — same values, same CLR types, same exception types on the invalid cases:

• identity, affine (x*2+1, 2*x), x/2
• (x - 32) * 5 / 9 — the integer-division trap, 100 under both
• Pow Sqrt Abs Round Log Log10 Exp Max Min, if(x > 0, x, 0)
• a bool-yielding comparison (x > 1 → True → 1), scientific notation (1e3 * x)
• the non-finite cases the code comments call out: x / 0 → Infinity, 0 / 0 → NaN, neither throws under either version, so the double.IsFinite guard still carries them
• invalid input: bogus(x) → NCalcFunctionNotFoundException, x + → NCalcParserException, y * 2 → NCalcParameterNotDefinedException — identical types, so HasValidExpression still goes false in the same three ways

The upgrade is behaviour-neutral for every expression this app can construct.

Other gates, on SDK 10.0.302 with CI=true

gate	result
locked restore, all six projects	succeeds, rewrites nothing
library / Desktop / AvaloniaCapture / iOS, Release	build succeeded, 0 errors
lock files after the iossimulator-arm64 build	untouched
unit tests	336/336 passed
check_dependabot_claims.py	claim applied

No new warnings — origin/main measured in the same worktree, --no-incremental, is 246 / 246 / 247 / 247, and this branch reports the same four.

One thing worth saying plainly: the reason this needed a hand-built probe is that the scaling path has no test. That gap outlives this PR and belongs in its own change, not here.

🤖 Generated with Claude Code

[tylerkron]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[tylerkron]

Rebased this by hand onto current main (c89dd02) — head is now 7fd2d74 and the PR is
MERGEABLE. The original commit went CONFLICTING once main's lock files moved underneath
it, and @dependabot rebase did not pick it up.

What changed vs. the old head, nothing but a re-derivation of the same bump:

• All six packages.lock.json files regenerated with a plain dotnet restore — no -r, so
  no RID narrowing and no NU1004 on CI's locked-mode restore. Verified the iOS lock still
  carries all three framework/RID sections (net10.0-ios26.5, /ios-arm64,
  /iossimulator-arm64), structurally identical to main.
• The lock diff is NCalc-only and symmetric (121 insertions / 121 deletions): NCalcSync
  6.4.0 → 7.1.0, NCalc.Core + NCalc.Parser replacing NCalc.Domain, Parlot
  3003.0.0.346 → 3003.2.0.161, ExtendedNumerics.BigDecimal 1.5.7 → 1.5.8, plus a transitive
  patch bump of Microsoft.Extensions.Logging.Abstractions 10.0.7 → 10.0.10.

Gate, run locally on 7fd2d74: Desktop head green, iOS head green
(-c Release -r iossimulator-arm64 --no-restore), dotnet test 424/424. The Android head
cannot build on this Mac (only the ios workload is installed) — CI covers it.

The part that was not verifiable before

This is a major version bump of the library that evaluates user-entered channel scaling
expressions — the x * 1.5 a user types, applied to every sample before it reaches the live
plot, the logging database and the CSV export. That path had no tests at all, so a green
build could not tell you whether a recorded reading comes out the same on 7.1.0. It only tells
you the app still compiles.

So I wrote characterisation tests for it and ran them against both versions from one working
tree, changing only the PackageReference with a plain restore between: 26/26 pass on 6.4.0
and 26/26 pass on 7.1.0, identically. They cover the arithmetic operators in double precision,
the built-in functions (Abs/Sqrt/Pow/Round/Max/Min), acceptance and rejection at
entry, the non-finite guard that keeps Infinity/NaN out of recorded data, and — the one with
real teeth — that a decimal literal still parses with a dot under a comma-decimal culture, since
a culture-sensitive parser would turn x * 1.5 into x * 15 for a de-DE user with no error
message anywhere.

Those tests are in #221, separately, so they land whether or not this bump does and guard the
next one too. Worth merging #221 first — then this PR's own CI exercises the new tests
against 7.1.0 rather than my local run being the only evidence.

Caveat that survives: the guarantee is coverage-shaped, not absolute. Every NCalc construct
reachable from ScaleExpression today is covered; a 7.x semantic change in some other NCalc
feature the app does not currently use would go unnoticed.