LiveScript 2.0.0

[celicoo]

Any plans for a second version?

[dk00]

Related discussions: #683, #705, #811, #821, #903, #910

I believe that converting LS AST to Babel AST is the most easier way to generate latest ES code, and already started working on it.

The preliminary convert function can handle Var, Assign, Block, Fun, converted AST of this:

a = -> (a) -> a = b = (b) -> a = b = it

generates this:

let a;

a = function (it) {
  return function (a) {
    let b;
    return a = b = function (b) {
      let a;
      return a = b = it;
    };
  };
};

Basic node types (Literal, Parens, Return, Chain, Call, Index, Key, Assign, Binary, Unary, Arr, Prop, Obj, If) will be added soon, and then import and export.

The plan is turn import to this at top scope into ES import, and an option for output type of export, so we can use import like using require!

import lodash
import lodash: _
import lodash: *: _
import lodash: {merge, set, omit: skip}
import \side-effect

or

import
  lodash
  lodash: _
  lodash: *: _
  lodash: {merge, set, omit: skip}
  'side-effect'

to

import lodash from 'lodash'
import _ from 'lodash'
import * as _ from 'lodash'
import {merge, set, omit as skip} from 'lodash'
import 'side-effect'

and

import options: location: {host, port}

to

import location$ from 'options'
const {host, port} = location$

and

export {name0: local, name1, module: {name2, alias: external}}

to

export {local as name0, name1}
export {name2, external as alias} from 'module'

[determin1st]

don't go to the dark side. const's, let's and other classes just go imerative way. It's right there, in Ecma, why not using ES? - just don't make LS worse.

[askucher]

I am interested. By the way, Livescript 2.0 should support html (jade's structure) syntax inside in order to use React

product-row = React.create-class do
  render: ->
    <tr
      <td
        <span
          if @props.product.stocked
            style:
              color: 'red'
          @props.product.name
      <td @props.product.price

[dk00]

We can use React in similar way at this time, with additional commas:

require! react: createElement: h
#Coming s∞n: import react: createElement: h

function product-row product: {stocked, name, price}
  h \tr,,
    h \td,,
      h \span if stocked then style: color: \red else,
        name
      h \td,, price

+1 for HTML-like syntax. Maybe we can omit < after first level?

function product-row product: {stocked, name, price}
  <tr
    td
      span if stocked then style: color: \red
        "#name"
    td "#price"
    "additional text"

[unclechu]

@askucher I don't see any profit of specific syntax for that, React already provides React.DOM object that you could use, it contains most of html-tags (React html-tags) that you need provided as object keys.
Example: https://bitbucket.org/unclechu/react-learn/src/210d9cd6a71d22f84cc2162010e77d37b291212e/src/js/main.ls?at=master&fileviewer=file-view-default#main.ls-60:83

[sra448]

I would very much welcome development on Livescript. It is my favourite compile-to-javascript language, but it gets increasingly more difficult to justify its use to customers and even employers, as everybody seems to love ES6 so much.

Personally, I think Livescript could use some streamlining (like, do we need it?). It would also be huge, if we were able to get some better tooling (like ESLint) and maybe even optional types (haskell style 😜 ).

[unclechu]

@sra448 I personally need it. Good type system would make LiveScript just perfect. I would personally just like to see custom operators in LiveScript, like we do it in Haskell.

[determin1st]

Separation of concerns?

[celicoo]

I think we need make official, we have the people to help, so let's do it! I think we need first create a repo like https://github.com/coffeescript6/discuss to discuss new implementations and collect some proposals.

[dk00]

The name livescript is taken but not used at all, could we claim it and use it as our organization name?

[sevvie]

I'd love to help with the development. I'm looking for a pet project.

…

On Sat, Jan 21, 2017 at 7:49 PM, dk00 ***@***.***> wrote: The name livescript <https://github.com/livescript> is taken but not used at all, could we claim <https://help.github.com/articles/name-squatting-policy/> it and use it as our organization name? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#943 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABlJuLMIcX6FHx1vDrQ0_S-4or1WO3m8ks5rUqeCgaJpZM4LWpWh> .

[KyelSinOo]

[gkz]

Re: @dk00 if you start a new project, I would prefer you choose a new name so there is no confusion (like I chose a new new when I forked coco)

[dk00]

@gkz
I'm working on an external version of #862 (discussed in #821), a function turns the result of LiveScript.ast code into something acceptable for Babel.transformFromAst or some other good ES code generators.

I'm satisfied with LiveScript and not going to start a new project.

[gkz]

Cool!