functionalscript / functionalscript

FunctionalScript is a purely functional subset of JavaScript

FunctionalScript

FunctionalScript is a purely functional programming language and a strict subset of ECMAScript/JavaScript. It's inspired by

• JSON and JSON5 as subsets of JavaScript. JSON is also a subset of FunctionalScript.
• asm.JS/WebAssembly, as a subset of JavaScript.
• TypeScript, as a superset of JavaScript.

A brief description of FunctionalScript Programming Language.

Create a new FunctionalScript repository on GitHub here.

Learn more about

• Purely Functional Programming in JavaScript,
• FunctionalScript.

Design Principles

In FunctionalScript:

• Any module is a valid JavaScript module. No additional build steps are required.
• Code should not have side-effects. Any JavaScript statement, expression, or function that has a side effect is not allowed in FunctionalScript. There are no exceptions to this rule, such as unsafe code, which can be found in Rust, C#, and other languages.
• A module can depend only on another FunctionalScript module.
• It also has no standard library. Only a safe subset of standard JavaScript API can be used without referencing other modules.

Applications

FunctionalScript code can be used:

• in any JavaScript/TypeScript application,
• as a JSON with expressions,
• as a query language.

Sponsors

• KirillOsenkov,
• antkmsft.

functionalscript's Issues

Simple validator (no type checking)

• parser
• AST
• minimizers (for pack module)
• analyzing locality (only declared objects can be used)

Test Framework should support `.d.cjs` files

https://github.com/functionalscript/functionalscript/blob/main/dev/module.mjs#L109

Fix decToBin function when overflow occurs after rounding

DJS

• rename fjson to djs (data javascript), File extensions: .d.cjs, .d.mjs, .d.js.
• use JS tokenizer
• identifiers {a:5}
• big int
• module.exports = ...
• constants const a = [3];module.exports = { a: a, b: a }.
  • Deserialization. Make sure we build the correct DAG. Test: const obj = deserialize('...'); if (obj.a !== obj.b) { throw "" }
  • Serialization. const _0=[3];module.exports={a:_0,b:_0}
• import const a = require('c.d.cjs');module.exports = { a: a, b: a}. Deserialization only.
• ES6 import import a from 'c.d.mjs';export default { a: a, b: a}.
• short form const a = 5;module.exports = { a }

Optional, for fun, syntax sugar:

• comments. Ignore them. Not an error.
• double/single quote strings

Support UInt8Array

It also can be used as a UTF8 string and an alternative to string type, since JS supports only UTF-16 strings.

This's an incorrect implementation because it doesn't convert UTF16 to UTF8 bytes.

Uint8Array.from(Array.from(text).map(letter => letter.charCodeAt(0)))

See

• https://stackoverflow.com/questions/62839519/how-convert-a-string-to-type-uint8array-in-nodejs
• https://stackoverflow.com/questions/54814215/node-js-buffer-vs-uint8array

Remove COM

Move nanocom Rust library to natfoam/lib repo and remove the com directory.

TypeScript vs JavaScript

https://link.medium.com/oKTXbzl5XBb

Unit tests on Bun and Deno

• Bun
• Deno

Samples?

Can there be a samples directory with an .md file on how to run them? ("run npm install, run npm run build")?

I think, the following samples could be beneficial:

1. "99 bottles of beer". Calls itself recursively starting from 99, special casing 1.
2. "sort numbers" - an equivalent of the following Haskell code:

quickSort []     = []
quickSort (x:xs) = quickSort (filter (<x) xs)
                   ++ [x] ++
                   quickSort (filter (>=x) xs)

3. Consume a FunctionalScript function from "existing" TypeScript project
4. Consume a FunctionalScript function from "existing" JavaScript project
5. Probably, "Hello World" (just to cover another classic example)
6. A parser? (where functional languages are strong). Could be a URL or DateTime parser.
7. Expression calculator (+, -, /, %, (), maybe pi constant, log2(), sin(), cos() etc) - the stuff similar to what a typical hardware calculator has.

ES6 modules.

The proposal is to use export default only, because the JSON module will be asserted as a export default module https://github.com/tc39/proposal-json-modules#proposed-semantics-and-interoperability

// config.f.mjs
export default {
  "a": 5
}

import config from "config.f.mjs"

Also, see https://stackoverflow.com/a/61581222/374845

Simplify `list` to support only 3 types: `null`, `[...]`, `() => [fist, ...]`

Remove NotEmpty and Concat.