capnweb 0.0.0-3d17ba1 → 0.0.0-409821

package/dist/index-bun.d.cts

@@ -22,12 +22,12 @@ interface RpcTargetBranded {
 // `any` into inference.
 type Stubable = RpcTargetBranded | ((...args: never[]) => unknown);
 type IsUnknown<T> = unknown extends T ? ([T] extends [unknown] ? true : false) : false; // Types that can be passed over RPC
-// The reason for using a generic type here is to build a serializable subset of structured
-//   cloneable composite types. This allows types defined with the "interface" keyword to pass the
+// The reason for using a generic type here is to build the serializable subset of RPC-compatible
+//   composite types. This allows types defined with the "interface" keyword to pass the
 //   serializable check as well. Otherwise, only types defined with the "type" keyword would pass.
 type RpcCompatible<T> = // Allow `unknown` as a leaf so records/interfaces with `unknown` fields remain compatible.
-(IsUnknown<T> extends true ? unknown : never) // Structured cloneables
-| BaseType // Structured cloneable composites
+(IsUnknown<T> extends true ? unknown : never) // RPC-compatible base values
+| BaseType // RPC-compatible composites
 | Map<T extends Map<infer U, unknown> ? RpcCompatible<U> : never, T extends Map<unknown, infer U> ? RpcCompatible<U> : never> | Set<T extends Set<infer U> ? RpcCompatible<U> : never> | Array<T extends Array<infer U> ? RpcCompatible<U> : never> | ReadonlyArray<T extends ReadonlyArray<infer U> ? RpcCompatible<U> : never> | { [K in keyof T as K extends string | number ? K : never]: RpcCompatible<T[K]> } | Promise<T extends Promise<infer U> ? RpcCompatible<U> : never> // Special types
 | Stub<Stubable> // Serialized as stubs, see `Stubify`
 | Stubable;

package/dist/index-bun.d.ts

@@ -22,12 +22,12 @@ interface RpcTargetBranded {
 // `any` into inference.
 type Stubable = RpcTargetBranded | ((...args: never[]) => unknown);
 type IsUnknown<T> = unknown extends T ? ([T] extends [unknown] ? true : false) : false; // Types that can be passed over RPC
-// The reason for using a generic type here is to build a serializable subset of structured
-//   cloneable composite types. This allows types defined with the "interface" keyword to pass the
+// The reason for using a generic type here is to build the serializable subset of RPC-compatible
+//   composite types. This allows types defined with the "interface" keyword to pass the
 //   serializable check as well. Otherwise, only types defined with the "type" keyword would pass.
 type RpcCompatible<T> = // Allow `unknown` as a leaf so records/interfaces with `unknown` fields remain compatible.
-(IsUnknown<T> extends true ? unknown : never) // Structured cloneables
-| BaseType // Structured cloneable composites
+(IsUnknown<T> extends true ? unknown : never) // RPC-compatible base values
+| BaseType // RPC-compatible composites
 | Map<T extends Map<infer U, unknown> ? RpcCompatible<U> : never, T extends Map<unknown, infer U> ? RpcCompatible<U> : never> | Set<T extends Set<infer U> ? RpcCompatible<U> : never> | Array<T extends Array<infer U> ? RpcCompatible<U> : never> | ReadonlyArray<T extends ReadonlyArray<infer U> ? RpcCompatible<U> : never> | { [K in keyof T as K extends string | number ? K : never]: RpcCompatible<T[K]> } | Promise<T extends Promise<infer U> ? RpcCompatible<U> : never> // Special types
 | Stub<Stubable> // Serialized as stubs, see `Stubify`
 | Stubable;