Gengora.Comptime 2.5.0

Gengora.Comptime

Gengora.Comptime is the generator-side engine for discovering, validating, evaluating, caching, and serializing [Comptime] methods and providers.

Use it

Generator packages reference it; ordinary application projects reference Gengora.Comptime.Attributes instead:

<PackageReference Include="Gengora.Comptime" PrivateAssets="all" />

A generator supplies its loaded Roslyn documents, diagnostic bag, policy, and cancellation token to ComptimeEvaluationEngine.Evaluate. Simple expressions use the in-process interpreter. Block bodies and supported invocations use the packaged worker process.

Use ComptimeEvaluationEngine.CreateSharedCache() only when a watch host should reuse results across engine instances. The disk cache is opt-in.

Methods containing a directly bound file or environment read admitted by the current policy run again instead of reading or writing either value cache. Changing the file or process environment can therefore change the next result without editing the method. Existing entries for these methods are ignored; unused permissions and pure methods keep their normal cache hits. This avoids hashing relative paths in the parent process when the worker has a different working directory. It does not track reads hidden behind helper calls or claim an operating-system sandbox. Re-evaluating external reads can cost more than a previous cache hit; that cost has not been measured.

Directly bound calls to source methods, including source extension methods, also bypass both value caches. Their helper bodies are outside the method-only key, so a helper edit must not return its previous value. Old entries are ignored and preserved. Declaring an uncalled helper does not prevent a pure method's hit. This is a conservative re-evaluation rule, not full dependency tracking: constructors, operators/conversions, implicit protocol calls, late-bound/dynamic, metadata-library, delegate, property and field dependencies remain separate. The extra worker cost has not been measured.

Boundary

The worker gives the host a hard timeout and process-tree cleanup boundary. It does not remove the current user's file, network, environment, or process permissions. Cross-generator ordering is not provided.

See the evaluation paths and limits.