@ball-lang/engine 1.4.3 → 1.4.5

package/dist/engine_setup.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"engine_setup.d.ts","sourceRoot":"","sources":["../src/engine_setup.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,MAAM,WAAW,YAAY;IAC3B,UAAU,EAAE,GAAG,CAAC;IAChB,gBAAgB,EAAE,GAAG,CAAC;IACtB,aAAa,EAAE,GAAG,CAAC;IACnB,WAAW,EAAE,GAAG,CAAC;IACjB,UAAU,CAAC,EAAE,GAAG,CAAC;IACjB,CAAC,CAAC,EAAE,MAAM,GAAG,GAAG,CAAC;CAClB;AAED,wBAAgB,iBAAiB,CAAC,GAAG,EAAE,YAAY;qBAoUzB,GAAG,2BAAuB,GAAG;qBA6E7B,GAAG,KAAG,GAAG;eAqCf,GAAG,KAAG,MAAM;;;;4BA8CZ,GAAG,GAAG,OAAO;0BACf,GAAG,GAAG,IAAI;qBACf,MAAM,SAAS,GAAG,WAAW,GAAG,GAAG,GAAG;;;yDAkJkB,GAAG,KAAG,IAAI;0CA0iBvB,IAAI;sCAshBR,IAAI;sCA0Bb,GAAG,KAAG,IAAI;uBArrDzB,GAAG,KAAG,OAAO;0BA2nCV,GAAG,KAAG,GAAG;EAgmBvC"}
+{"version":3,"file":"engine_setup.d.ts","sourceRoot":"","sources":["../src/engine_setup.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AAEH,MAAM,WAAW,YAAY;IAC3B,UAAU,EAAE,GAAG,CAAC;IAChB,gBAAgB,EAAE,GAAG,CAAC;IACtB,aAAa,EAAE,GAAG,CAAC;IACnB,WAAW,EAAE,GAAG,CAAC;IACjB,UAAU,CAAC,EAAE,GAAG,CAAC;IACjB,CAAC,CAAC,EAAE,MAAM,GAAG,GAAG,CAAC;CAClB;AAED,wBAAgB,iBAAiB,CAAC,GAAG,EAAE,YAAY;qBAoUzB,GAAG,2BAAuB,GAAG;qBA6E7B,GAAG,KAAG,GAAG;eAqCf,GAAG,KAAG,MAAM;;;;4BAsDZ,GAAG,GAAG,OAAO;0BACf,GAAG,GAAG,IAAI;qBACf,MAAM,SAAS,GAAG,WAAW,GAAG,GAAG,GAAG;;;yDAkJkB,GAAG,KAAG,IAAI;0CAikBvB,IAAI;sCAshBR,IAAI;sCA0Bb,GAAG,KAAG,IAAI;uBAptDzB,GAAG,KAAG,OAAO;0BA0pCV,GAAG,KAAG,GAAG;EAgmBvC"}

package/dist/engine_setup.js

@@ -496,8 +496,16 @@ export function createEngineSetup(mod) {
         if (Array.isArray(v))
             return '[' + v.map(__bts).join(', ') + ']';
         if (v instanceof Map) {
+            // NOT `v.entries()` — the compiled engine's own preamble shadows
+            // `Map.prototype.entries` with a Dart-style GETTER (returning an array
+            // of {key,value} objects, matching Dart's `Map.entries` property) so
+            // Ball's `.entries` field access works. That shadow makes `v.entries`
+            // non-callable, so `v.entries()` throws "not a function" for any real
+            // Map value. Iterate the Map directly instead — a Map's default
+            // iterator already yields [key, value] pairs and is unaffected by the
+            // entries/keys/values property shadowing.
             const parts = [];
-            for (const [k, val] of v.entries())
+            for (const [k, val] of v)
                 parts.push(__bts(k) + ': ' + __bts(val));
             return '{' + parts.join(', ') + '}';
         }
@@ -1164,8 +1172,17 @@ export function createEngineSetup(mod) {
         _r('string_to_int', (i) => {
             const m = _m(i);
             const s = String(m['value'] ?? m['string'] ?? i ?? '').trim();
+            // `.message` must be the bare invalid text (Dart's `FormatException.message`
+            // is never prefixed with the type name — only `.toString()` adds that).
+            // Setting `name: 'FormatException'` (not just a `message` override) lets
+            // the default `Error.prototype.toString()` ("name: message") produce the
+            // Dart-correct "FormatException: <text>" for anything that prints the
+            // caught exception itself rather than `.message`. Previously the message
+            // override clobbered the "FormatException: " prefix right back out,
+            // leaving `.name` as the native "Error" — undetected because no
+            // conformance fixture prints a caught FormatException directly.
             if (!/^-?\d+$/.test(s))
-                throw Object.assign(new Error('FormatException: ' + s), { __type__: 'FormatException', message: s });
+                throw Object.assign(new Error(s), { name: 'FormatException', __type__: 'FormatException' });
             return parseInt(s, 10);
         });
         _r('writeCharCode', (i) => { const m = _m(i); const self = m['self']; if (typeof self === 'object' && self !== null) {
@@ -1234,8 +1251,22 @@ export function createEngineSetup(mod) {
             return true;
         });
         _r('concat', (i) => { const m = _m(i); return String(m['left'] ?? '') + String(m['right'] ?? ''); });
-        _r('null_check', (i) => { const m = _m(i); const v = m['value'] ?? i; if (v == null)
-            throw new Error('Null check operator used on a null value'); return v; });
+        // `?? i` (used by most unary helpers below) can't distinguish "no `value`
+        // field" from "`value` is explicitly null" — for every OTHER helper that's
+        // harmless (a null numeric/string arg just coerces away), but for
+        // null_check it inverts the function's entire purpose: `x!` where `x` is
+        // null must throw (matches the Dart engine's `_extractUnaryArg` + null
+        // check — see engine_std.dart's 'null_check' and its
+        // "throws BallRuntimeError on null" test), yet `m['value'] ?? i` silently
+        // fell back to the (truthy) input map and returned it instead of
+        // throwing. hasOwnProperty-gate so an explicit null is honored.
+        _r('null_check', (i) => {
+            const m = _m(i);
+            const v = Object.prototype.hasOwnProperty.call(m, 'value') ? m['value'] : i;
+            if (v == null)
+                throw new Error('Null check operator used on a null value');
+            return v;
+        });
         _r('compare_to', (i) => {
             const m = _m(i);
             const l = m['left'] ?? m['value'] ?? m['self'] ?? m['a'] ?? 0;