porffor 0.59.7 → 0.59.8

package/compiler/codegen.js

@@ -1464,7 +1464,7 @@ const asmFuncToAsm = (scope, func, extra) => func(scope, {
 
 const asmFunc = (name, func) => {
   func = { ...func };
-  let { wasm, params, locals: localTypes, localNames = [], table, usesTag, returnTypes, returnType } = func;
+  let { wasm, params = [], locals: localTypes = [], localNames = [], table, usesTag, returnTypes, returnType } = func;
   if (wasm == null) { // called with no built-in
     log.warning('codegen', `${name} has no built-in!`);
     wasm = [];

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "porffor",
   "description": "An ahead-of-time JavaScript compiler",
-  "version": "0.59.7",
+  "version": "0.59.8",
   "author": "Oliver Medhurst <honk@goose.icu>",
   "license": "MIT",
   "scripts": {},

package/runtime/index.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import fs from 'node:fs';
-globalThis.version = '0.59.7';
+globalThis.version = '0.59.8';
 
 // deno compat
 if (typeof process === 'undefined' && typeof Deno !== 'undefined') {

package/AGENT.md

@@ -1,20 +0,0 @@
-you are an assistant coder for Porffor - an early javascript and typescript to webassembly and native ahead-of-time compiler. the codebase is written in js and ts.
-
-- built-ins apis (Date, String.prototype, etc) are written in ts inside `compiler/builtins`
-- once you update a file inside that directory, you MUST run `./porf precompile` to compile to make your changes effective
-- test your work using the test262 tools available, iterate independently but do not get stuck on one chain of thought or approach. paths for test262 tools should be relative to the 'test262/test' directory (e.g., 'built-ins/RegExp' NOT 'test262/test/built-ins/RegExp').
-- to get an overview of the most failing directories, use the command: `node test262/fails.cjs`
-- to just evaluate code in the engine, use the command: `./porf -p "..."`
-- after finishing, check if your work/diff could be simplified
-- always use single quotes (unless double is required)
-- 2-space indentation, LF line endings, no trailing whitespace
-- built-in APIs in `compiler/builtins/` written in TypeScript
-- inline code in built-ins, avoid helper functions
-- use semicolons
-- do not use trailing commas
-- use const/let, avoid var
-- follow existing naming: camelCase for variables, PascalCase for types
-
-memories:
-- The user prefers that prototype functions not have explicit return types in this codebase.
-- The user prefers not to use global variables in built-in functions.