forivall / tacoscript Goto Github PK

use pirates

• Add tests
• Properly pass options to comal

• parse
  • change ast node to be closer to a CallExpression
• transform
• generate

• Implement
  • Allow multiline input in REPL -- see coffeescript
• Test

like xo --init, etc, will set up a project to use tacoscript

• parse
• transform
• generate
  • expression
  • statement
• clean up with comal-traverse Path features (.get) -- document it more.

• parse
• transform
• generate

• parse
  • store metadata that this was a paren-less call
• generate (requires inference)

https://github.com/forivall/tacoscript/blob/master/doc/auto-const.md

see tacotruck printer/buffer.js

So consider the following:

const inject = (ƒunction) => (initial) => (iterable) => reduce(ƒunction, initial, iterable)

When using functions:

function inject (ƒunction) {
  return function injectWithInitial (initial) {
    return function injectWithInitialAndIterable (iterable) {
      return reduce(ƒunction, initial, iterable)
    }
  }
}

This can get cumbersome.

With tacoscript:

function inject(ƒunction) ->
  return function injectWithInitial (initial) ->
    return function injectWithInitialAndIterable (iterable) ->
      return reduce(ƒunction, initial, iterable)

Which becomes much easier to read, however consider the following improvement:

function inject(ƒunction) -> (initial) -> (iterable) ->
  return reduce(ƒunction, initial, iterable)

on branch allow-indent-before-newline-dot

still continue to re-export tacoscript from cli package

• Create cst-aware js generator; use cst data when generating javascript
  • Clone the tree, replace tacoscript cst elements with js cst elements,
    then simply print the CST.

• Create CST when parsing
• Add CST elements to Javascript AST
• #20 - Create tacoscript generator that is CST aware
• #21 - Create javascript generator that is CST aware
• Preserve CST in transforms
  • first, manually in transforms - helpers in comal-types to set CST data
  • second, automatically in comal-traverse - place whitespace from nodes removed in "replaceWith" into their replacement nodes.
• Analyse source CST and when converting to translated CST, try to use most commonly used pattern for given node pattern

• Use cst data when generating tacoscript
  • Instead of pushing tokens to a continuous token stream, enrich the ast
    with cst elements. https://github.com/estools/escodegen/wiki/CST-Proposals

• parse
• generate

core -> horchata
IIFE -> tacoscript-iife

make them parsable (maybe JSON) and create a script to automatically merge them with babel's AST docs.

also add compile operation that will use babel plugins to compile ast into es5

• Force plugins to provide their requirements in semver, & don't load
  incompatible plugins.
  • plugins should target comal version, parser name & version and generator name & version
    • generator should also declare if it needs cst info

https://github.com/tc39/tc39-notes/blob/master/meetings/2016-09/sept-27.md#11ic-generator-arrow-functions

tc39 has agreed on =>*, tacoscript currently uses *=> and *-> (IIRC)

and then use that readme template thing that @jonschlinkert uses

• parse
• transform
• generate
• e2e test