Class CanonicalDependencyFingerprint
java.lang.Object
org.ek9lang.compiler.common.CanonicalDependencyFingerprint
THE canonical fingerprint of a project's declared dependencies (D10, P3; docs/implementation/EK9_P2_P3_PLAN.md
ยง2.1):
deps, devDeps and excludeDeps, each turned into its own sorted name=version
block (so the result does not depend on HashMap iteration order), the three blocks kept in FIXED slots
(deps, devDeps, excludeDeps) separated by "\n" so an entry moving from one dict to another changes the
fingerprint even when the dict as a whole is otherwise empty. This REPLACES the HashMap.toString()
concatenation Ek9SourceVisitor.getDependencyFingerPrint() used before P3 - deterministic only by
accident of HashMap's order - so a committed ek9.lock's declared line is stable across
JVMs and runs. cli.CanonicalDependencyFingerprint (compiler-services) would have been the natural name
per the plan's lane table, but compiler-main cannot depend on compiler-services and
Ek9SourceVisitor.getDependencyFingerPrint() (compiler-main) is the one caller that must stay in sync
with ek9.lock's own fingerprint - so this lives here instead; compiler-services' lock classes
(THE example: cli.DependencyLockCurrency) import it normally (compiler-services already depends on
compiler-main). Hold one; never a static method.-
Constructor Summary
Constructors -
Method Summary
-
Constructor Details
-
CanonicalDependencyFingerprint
public CanonicalDependencyFingerprint()
-
-
Method Details
-
apply
-