precomputed-optional-parameter

Avoid redundant expensive computation by passing pre-computed results to internal helper methods as optional parameters. This pattern allows public APIs to delegate execution without triggering duplicate heavy work, preserving backward compatibility for existing internal callers.

The optional parameter pattern for precomputed values involves inner helpers accepting a nullable argument that defaults to null. Helpers use null-coalescing guards to compute the data only when the caller does not provide a precomputed value.

Optimize PowerShell runspace initialization by passing precomputed session introspection data to delegation methods. This prevents the inner helper from triggering a second costly runspace creation during its own initialization phase.

Maintain backward compatibility by adding optional precomputed parameters with null defaults to existing method signatures. Promote sealed inner helper types to internal visibility if they must appear in the public API signature.

Use null-coalescing guards for expensive data computation when a public method computes heavy data and delegates to an inner helper. The guard ensures the helper computes the data only if the caller passes a null precomputed parameter.

The best way to prevent duplicate work in nested C# helper methods is establishing a responsibility model where the public API layer computes and passes the expensive data. The inner helper uses null-coalescing to process the provided value or recompute it.