mirror of
https://github.com/luxfi/zap.git
synced 2026-10-30 15:04:16 +00:00
zeekay
af88152c6f
There is one perfected typed ZAP layer and it lives at github.com/luxfi/zap/v1 — forwards-only, no backwards-compat baggage, never a breaking major. Mechanical, behavior-preserving: v2/ -> v1/ (git mv), package zapv2 -> zapv1, import path .../zap/v2 -> .../zap/v1 (incl. the codegen's emitted banner + import so generated files reference /v1). Codegen golden tests pass; typed layer vets clean. (Pre-existing CGO 'resolv' link failures in the root package are unrelated env noise.)
23 lines
929 B
Go
23 lines
929 B
Go
// Copyright (C) 2026, Lux Industries Inc. All rights reserved.
|
|
// See the file LICENSE for licensing terms.
|
|
|
|
// Package zap (v1) is deprecated for new schema authoring.
|
|
//
|
|
// New schemas MUST be authored via codegen (~/work/lux/zap/v2/codegen)
|
|
// which emits v1-equivalent fast paths from a declarative .zap source.
|
|
//
|
|
// Consumer dispatch for ad-hoc / dynamic schemas goes through the v2
|
|
// generic API (github.com/luxfi/zap/v1).
|
|
//
|
|
// The v1 hand-rolled code in this package remains for in-flight
|
|
// migration of legacy callers (luxfi/node/vms/platformvm/txs/zap_native,
|
|
// parts of luxfi/consensus/protocol/quasar, etc.); no new v1 schemas
|
|
// are accepted.
|
|
//
|
|
// The wire format is unchanged across v1 and v2 — this is a code-level
|
|
// decomplection of the authoring surface only. Existing v1 buffers
|
|
// remain parseable by both v1 and v2.
|
|
//
|
|
// See ~/work/lux/zap/v2/README.md for the canonical authoring path.
|
|
package zap
|