@scriptc/cli-darwin-arm64 0.0.0 → 0.2.1

package/dist/lib/declarations/scriptc-overrides.d.ts

@@ -0,0 +1,92 @@
+/* scriptc's divergence and precision overrides — interface merges that
+ * re-type a handful of standard-library members to scriptc's documented
+ * runtime behavior. Merged interfaces resolve overloads later-declaration-
+ * first, so these win at call sites that match them; call forms only the
+ * lib signatures accept still typecheck and are fenced by the lowerer.
+ *
+ * This file is part of the LOWERING program only. Preflight's second-chance
+ * pass (checkPreflight) rebuilds the program WITHOUT it — the project's own
+ * type world — so a program that typechecks under its own tsc is never
+ * rejected over an override-manufactured error; the affected sites meet the
+ * lowerer's honest fences instead (SC1100's checked-cast family for
+ * JSON.parse results, the executor fences for Promise shapes). The
+ * primitives every world needs (comptime, setTimeout, __island_eval) live
+ * in scriptc.d.ts, which ships to BOTH programs. */
+
+/* `at(): string`, not the lib's `string | undefined`: undefined is
+ * unrepresentable, so an out-of-range at() THROWS a catchable TypeError at
+ * the validated island exit instead of returning undefined (documented
+ * divergence, SEMANTICS.md). */
+interface String {
+  at(index: number): string;
+}
+
+/* Object.values/entries with the actual field-value union, not the lib's
+ * `any` (the lib's precise overloads only cover index-signature and
+ * ArrayLike sources). A PRECISION override, not a divergence: the lowering
+ * emits the field list statically and the values are exactly T[keyof T] —
+ * without this the result would be `any`-typed and drag every downstream
+ * use into the island. An opaque object has no statically known keys;
+ * its actual values remain unknown instead of becoming an impossible
+ * never payload. */
+interface ObjectConstructor {
+  values<T extends object>(o: T): Array<keyof T extends never ? unknown : T[keyof T]>;
+  entries<T extends object>(o: T): Array<[string, keyof T extends never ? unknown : T[keyof T]]>;
+}
+
+/* `parse` returns `unknown`, not the lib's `any` — the dynamic boundary. A
+ * checked cast (`JSON.parse(s) as Config`) validates the value against the
+ * target type at runtime and THROWS on mismatch — the mechanism that makes
+ * trusting TS types sound at data boundaries. Reviver results use the same
+ * checked boundary. A function replacer can omit the root, so that form
+ * returns string | undefined even though the stock lib promises string.
+ *
+ * `stringify` takes `unknown`, not the lib's `any`: the same honest
+ * surface, but the parameter must not CONTEXTUALLY TYPE literal arguments
+ * as `any` (an any-typed slot is the island boundary; `JSON.stringify([1,
+ * 2])` must keep building a static array and serializing it
+ * type-directedly). */
+interface JSON {
+  parse(text: string): unknown;
+  parse(text: string, reviver: (this: unknown, key: string, value: unknown) => unknown): unknown;
+  stringify(value: unknown): string;
+  stringify(value: unknown, replacer: (this: unknown, key: string, value: unknown) => unknown, space?: string | number): string | undefined;
+}
+
+/* The supported Promise construction shape: an executor whose resolve takes
+ * the plain value. Preferred over the lib signature at inference time, so
+ * `new Promise<T>((resolve) => ...)` types resolve as `(value: T) => void`
+ * — no PromiseLike union. The reject parameter is a real closure rejecting
+ * the promise; its reason is pinned to Error (the lib says `reason?: any`)
+ * because rejection payloads ride the same representation as thrown values
+ * and the idiomatic reason IS an Error — reject(nonError) and bare
+ * reject() typecheck only in the project world and meet the lowerer's
+ * honest coercion fences instead. First settle wins, exactly JS: a reject
+ * after resolve (or a second reject) is a no-op, and an executor throw
+ * after any settle is swallowed. Executors that use the lib signature's
+ * other extras (resolving with a thenable) still typecheck and fail
+ * lowering on their types. */
+interface PromiseConstructor {
+  new <T>(
+    executor: (resolve: (value: T) => void, reject: (reason: Error) => void) => void,
+  ): Promise<T>;
+  /* ES2024's Promise.withResolvers, in the executor's own scriptc shape:
+   * resolve takes the plain value (no PromiseLike union; the conditional
+   * collapses Promise<void>'s resolve to () => void so the record's
+   * field types map exactly), reject is the executor's Error-pinned
+   * rejection closure. The lib's own declaration would otherwise be
+   * unrepresentable field-by-field. */
+  withResolvers<T>(): {
+    promise: Promise<T>;
+    // `0 extends 1 & T` detects any (untyped JS: Promise.withResolvers()
+    // infers it) — its settled value rides the dyn arm like unknown's,
+    // so resolve takes one unknown; a naked conditional over any would
+    // otherwise union BOTH branches, which no field can map.
+    resolve: 0 extends 1 & T
+      ? (value: unknown) => void
+      : [T] extends [void]
+        ? () => void
+        : (value: T) => void;
+    reject: (reason: Error) => void;
+  };
+}

package/dist/lib/declarations/scriptc.d.ts

@@ -0,0 +1,98 @@
+/* scriptc's shipped declarations — the ALWAYS-SHIPPED CORE. Programs
+ * compile against the TypeScript ES standard library without lib.dom and
+ * the project's @types/node when present: the checker sees the standard
+ * surface, and the LOWERER is the scope fence — any reached use of it
+ * without a lowering is a SC2020 diagnostic at its use site. This file
+ * declares only what that ES-only library does not:
+ *
+ * 1. scriptc's own primitives (comptime, __island_eval).
+ * 2. The RequestInfo type alias, supplied by the default DOM lib in ordinary
+ *    TypeScript projects but absent from @types/node's globals.
+ * 3. setTimeout/clearTimeout and the Timeout handle (Node/dyn territory the
+ *    lib files don't cover; plain declarations, so with @types/node present
+ *    they MERGE as overloads instead of colliding — the Timeout handle maps
+ *    to the numeric timer id either way, and .unref()/.ref()/.hasRef() are
+ *    loop-liveness bookkeeping).
+ *
+ * This file ships to EVERY program scriptc builds — the lowering program
+ * and preflight's project-world second-chance program alike (a project
+ * using comptime must typecheck in both). The divergence/precision
+ * overrides (JSON.parse(): unknown, the Promise executor shape,
+ * ...) live in scriptc-overrides.d.ts, which joins the LOWERING program only.
+ *
+ * console, process, and the "node:fs" module live in scriptc-node-fallback.d.ts,
+ * shipped ONLY when the target project has no @types/node — with it, the
+ * project's real Node types are the type surface and the fallback stands
+ * down (its `declare const`/`declare module` forms would collide). The
+ * lowering tables recognize the same members either way, by name +
+ * provenance. */
+
+/* The default TypeScript DOM lib supplies this name even for Node projects.
+ * scriptc uses the ES lib and @types/node's fetch globals instead, while the
+ * fallback fetch declarations use the same alias. It is only a type: runtime
+ * fetch/Request support remains governed by the lowering fences. */
+type RequestInfo = string | URL | Request;
+
+/* Node exposes the codec constructors globally, but older @types/node
+ * versions rely on lib.dom for their instance type names. Keep those types
+ * available in the ES-only program as well as the fallback type world. */
+interface TextEncoder {
+  readonly encoding: string;
+  encode(input?: string): Uint8Array;
+  encodeInto(source: string, destination: Uint8Array): { read: number; written: number };
+}
+interface TextDecoder {
+  readonly encoding: string;
+  readonly fatal: boolean;
+  readonly ignoreBOM: boolean;
+  decode(input?: ArrayBuffer | DataView | Int8Array | Uint8Array | Uint8ClampedArray | Int16Array | Uint16Array | Int32Array | Uint32Array | Float32Array | Float64Array | BigInt64Array | BigUint64Array, options?: { stream?: boolean }): string;
+}
+
+/* The timer handle — setTimeout's return, mapped to the numeric timer id.
+ * unref() drops it from the event loop's keep-alive set (the process may
+ * exit with the timer still armed — it never fires then, exactly Node);
+ * ref() restores it; hasRef() reports the state. The methods return the
+ * handle for chaining. Under @types/node this MERGES with NodeJS.Timeout
+ * (both map to the same numeric handle). */
+interface Timeout extends Disposable {
+  ref(): Timeout;
+  unref(): Timeout;
+  hasRef(): boolean;
+  /* Re-arms the timer to fire at now + the original delay (Node's
+   * Timeout.refresh). Chaining like ref/unref. */
+  refresh(): Timeout;
+  [Symbol.dispose](): void;
+}
+/* The callback is invoked with NO arguments; the second overload admits a
+ * callback declared with one parameter for the sleep idiom —
+ * `setTimeout(resolve, ms)` with Promise<unknown>'s resolve — where the
+ * zero-argument invocation delivers undefined (@types/node's generic
+ * signature admits the same shape and MERGES with these). Promise<void>'s
+ * resolve keeps matching the first overload (void params accept absence). */
+declare function setTimeout(callback: () => void, ms?: number): Timeout;
+declare function setTimeout(callback: (value?: unknown) => void, ms?: number): Timeout;
+/* The trailing-argument form: Node passes the extras to the callback
+ * (`setTimeout(cb, 0, 'foo')` fires cb('foo')). The callback slot accepts
+ * any function shape (never[] rest — parameter-contravariance's bottom);
+ * the delivered call rides the checked-dynamic boundary, so each argument
+ * is validated against the callback's real signature at fire time. */
+declare function setTimeout(callback: (...args: never[]) => void, ms?: number, ...args: unknown[]): Timeout;
+declare function clearTimeout(handle?: Timeout | number | null | undefined): void;
+
+/* Compile-time evaluation. The callback must be an inline arrow/function
+ * expression with NO references to outer bindings (it is extracted
+ * source-textually and executed in an isolated node:vm context inside the
+ * COMPILER's Node process); the returned value is baked into the binary as a
+ * literal — numbers (finite), strings, booleans, arrays, and records,
+ * nested. What type-checks runs with real JavaScript semantics, so the
+ * baked result is exactly what Node would compute at runtime (the
+ * differential harness verifies this with a `comptime = (f) => f()` shim). */
+declare function comptime<T>(compute: () => T): T;
+
+/* INTERNAL TESTING HOOK — not part of the supported surface, deliberately
+ * undocumented. Evaluates `code` in the embedded dynamic-island engine and
+ * returns String(result); island exceptions arrive as catchable errors.
+ * Requires --dynamic (a clean diagnostic otherwise). This exists to prove
+ * the engine embed end-to-end in tests; user-facing constructs will lower
+ * to the island through their own paths, not through this. */
+declare function __island_eval(code: string): string;

package/dist/lib/llvm/LICENSE

@@ -0,0 +1,278 @@
+==============================================================================
+The LLVM Project is under the Apache License v2.0 with LLVM Exceptions:
+==============================================================================
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+    TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+    1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+    2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+    3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+    4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+    5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+    6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+    7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+    8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+    9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+    END OF TERMS AND CONDITIONS
+
+    APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+    Copyright [yyyy] [name of copyright owner]
+
+    Licensed under the Apache License, Version 2.0 (the "License");
+    you may not use this file except in compliance with the License.
+    You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+
+
+---- LLVM Exceptions to the Apache 2.0 License ----
+
+As an exception, if, as a result of your compiling your source code, portions
+of this Software are embedded into an Object form of such source code, you
+may redistribute such embedded portions in such Object form without complying
+with the conditions of Sections 4(a), 4(b) and 4(d) of the License.
+
+In addition, if you combine or link compiled forms of this Software with
+software that is licensed under the GPLv2 ("Combined Software") and if a
+court of competent jurisdiction determines that the patent provision (Section
+3), the indemnity provision (Section 9) or other Section of the License
+conflicts with the conditions of the GPLv2, you may retroactively and
+prospectively choose to deem waived or otherwise exclude such Section(s) of
+the License, but only in their entirety and only with respect to the Combined
+Software.
+
+==============================================================================
+Software from third parties included in the LLVM Project:
+==============================================================================
+The LLVM Project contains third party software which is under different license
+terms. All such code will be identified clearly using at least one of two
+mechanisms:
+1) It will be in a separate directory tree with its own `LICENSE.txt` or
+   `LICENSE` file at the top containing the specific license and restrictions
+   which apply to that software, or
+2) It will contain specific license and restriction terms at the top of every
+   file.
+
+==============================================================================
+Legacy LLVM License (https://llvm.org/docs/DeveloperPolicy.html#legacy):
+==============================================================================
+University of Illinois/NCSA
+Open Source License
+
+Copyright (c) 2003-2019 University of Illinois at Urbana-Champaign.
+All rights reserved.
+
+Developed by:
+
+    LLVM Team
+
+    University of Illinois at Urbana-Champaign
+
+    http://llvm.org
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal with
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+    * Redistributions of source code must retain the above copyright notice,
+      this list of conditions and the following disclaimers.
+
+    * Redistributions in binary form must reproduce the above copyright notice,
+      this list of conditions and the following disclaimers in the
+      documentation and/or other materials provided with the distribution.
+
+    * Neither the names of the LLVM Team, University of Illinois at
+      Urbana-Champaign, nor the names of its contributors may be used to
+      endorse or promote products derived from this Software without specific
+      prior written permission.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
+FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE
+SOFTWARE.