porffor 0.37.9 → 0.37.10
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -2
- package/package.json +1 -1
- package/runner/index.js +1 -1
package/README.md
CHANGED
|
@@ -273,7 +273,7 @@ Currently, Porffor is seriously limited in features and functionality, however i
|
|
|
273
273
|
- More in future probably?
|
|
274
274
|
|
|
275
275
|
## Todo
|
|
276
|
-
No particular order and no
|
|
276
|
+
No particular order and no guarantees, just what could happen soon™
|
|
277
277
|
|
|
278
278
|
- Asur
|
|
279
279
|
- Support memory
|
|
@@ -327,7 +327,7 @@ Porffor intentionally does not use Wasm proposals which are not commonly impleme
|
|
|
327
327
|
### 2. Why at all?
|
|
328
328
|
Yes!
|
|
329
329
|
|
|
330
|
-
|
|
330
|
+
### 3. Isn't this the same as AssemblyScript/other Wasm langs?
|
|
331
331
|
No. they are not alike at all internally and have very different goals/ideals:
|
|
332
332
|
- Porffor is made as a generic JS engine, not for Wasm stuff specifically
|
|
333
333
|
- Porffor primarily consumes JS
|
package/package.json
CHANGED