Sam De Roeck

Fix TypeSystem reference model to prevent leaks on recursive types Summary: The existing all-`Arc` model cannot represent recursive types (e.g. `struct Tree { children: list<Tree> }`) without leaking: every inter-node edge holds a strong reference, forming cycles that never reach refcount zero. This switches user-defined edges to `Weak` (while keeping `Arc` for held handles returned by `get()`), so the TypeSystem is the sole strong owner and cycles are broken. Structured fields use deferred initialization via `UnsafeCell<Option<_>>` to allow the builder to create all nodes before resolving cross-references. Also restructures nodes into per-file modules, adds `StructuredNode` trait, `BasicTypeSystem`, and `TypeSystem` trait with `TypeId` resolution. Reviewed By: praihan Differential Revision: D108476964 fbshipit-source-id: 09389ce6be3bed77e9fadf5d329c4938dbeadc2f

ServiceCatalogDigest Summary: Add deterministic `ServiceCatalog` and `ServiceDescriptor` digests, inspired by the `TypeSystemDigest` equivalents. Equivalent to `TypeSystemDigest`, the runtime representations (e.g. `ServiceCatalog` and its nodes) will provide an equivalent digest to the serialized representations (e.g. `SerializedServiceCatalog`). In addition, it is also fully platform independent, so the digest can be calculated deterministically in all supported languages & on all supported architectures. Rust port of D110799794. Differential Revision: D110917277 fbshipit-source-id: 3b182fe8f74a7eabcd9819b2772f1092a1885f6d

ServiceCatalogDigest Summary: Add deterministic `ServiceCatalog` and `ServiceDescriptor` digests, inspired by the `TypeSystemDigest` equivalents. Equivalent to `TypeSystemDigest`, the runtime representations (e.g. `ServiceCatalog` and its nodes) will provide an equivalent digest to the serialized representations (e.g. `SerializedServiceCatalog`). In addition, it is also fully platform independent, so the digest can be calculated deterministically in all supported languages & on all supported architectures. Reviewed By: iahs Differential Revision: D110799794 fbshipit-source-id: bcbe31bbd7bb68bc65d32c7019921bad20d25443

Implement TypeSystemDigest for runtime type system nodes Summary: Implements the `TypeSystemDigest` trait for all runtime node types, producing an identical digests to the C++ `TypeSystemDigest` implementation. This enables cross-language cache invalidation, version compatibility checks, and deduplication between C++, Rust, and future Python/Hack runtimes. Reviewed By: praihan Differential Revision: D108641538 fbshipit-source-id: e6738ae28327f0c07e1f9a07b53024f01aceb4e5

Execute transcode plans on the interpreter Summary: Add `TranscodeInterpreter`, an interpreter-style execution engine that walks `TranscodePlan` tree and invokes the shared cursor/protocol intrinsics to read one encoding and write another. ___ Differential Revision: D110793295 fbshipit-source-id: 16b393b6587bdccb9a22f0a1380e06385e6523e6

Golden test fixtures Summary: Adds golden protocol coverage for representative Thrift shapes so interpreter changes can be checked against Compact, Binary, and JSON serializer behavior. ___ Differential Revision: D112931048 fbshipit-source-id: cd5769cc3ae2483945826da1809e9bea67cb70e5

Read JSON input on the interpreter Summary: Teaches the `interpreter` engine to consume JSON sources for structs, arrays, scalars, and maps, including default emission, union validation, unknown-field skipping, and map key coercion. ___ Differential Revision: D112926691 fbshipit-source-id: 8b1f3f47c75c8c188a2d790cea0572fbca4fd61d

Add Go TypeSystem digest support Summary: Adds a Go package for `TypeSystemDigest`, i.e. the canonical SHA-256 language-independent hash for thrift types & schemas. The implementation follows the same composition model as the Rust `TypeSystemDigest` trait: top-level digestable values expose `Digest` and `DigestWithMode`, and every nested digestable node contributes bytes through `hashInto`. Generated thrift values and scalar primitives are adapted into that interface, so the hasher only owns raw byte writing and ordering helpers. ___ Differential Revision: D113784936 fbshipit-source-id: 89948f340289775ebadab5a0788978601288c37f

Parse and emit JSON scalar values Summary: The JSON leaf endpoint of the wire layer: - decimal number parse and format - escape-aware quoted-string parse and format - a strict true/false keyword reader - recursive value skipping JSON is the untrusted REST-facing edge, so the reader validates every byte it consumes rather than trusting a producer. The object and array framing around these leaves is handled higher up by the engines. ___ Reviewed By: iahs Differential Revision: D110531079 fbshipit-source-id: 4e0569a69dca995a2c97a835ed0df1e0d3ec8bdb

Share the byte primitives common to every wire format Summary: The base of the wire layer: the byte primitives every protocol reuses. - varints, plain and zigzag - fixed-width integers - length-prefixed byte ranges - the `WireType` guard over Thrift's `TType` These are the extern "C" symbols the JIT resolves and the interpreter calls, so both engines share one implementation of the hot primitives and every per-protocol framing layer builds on the same base. ___ Differential Revision: D110530595 fbshipit-source-id: f544f8f6d91eae2b2b1bd163bd24dfc40e9200b4