Livescript 2.0

[neersighted]

Livescript 2.0

Discuss Livescript 2.0 here. Please break major components of 2.0 into separate issues.

Progress

• Rewrite with the Redux compiler, and generate a Mozilla JS AST: Rewrite with the Coffeescript Redux compiler #262, Generate JS AST #125
  • Support source maps
  • Generate a Mozilla JS AST
  • Generate code from AST with escodegen
  • <further details from @gkz here>
• Type inference and verification: Idea: Type Inference #30
• ECMAScript 6 features: ES6 #26
• Remove legacy features: removing features #219
• Overhaul Prelude.ls: Create extension system prelude-ls#45
  • Extension system
  • <further details from @gkz here>
• Overhaul slake: Slake overhaul  #225
  • Task dependencies
  • Function-oriented: currying, piping vs inheritance, subclassing, and chaining
  • Helper functions
• Match (psuedo pattern-matching): Pseudo pattern matching #109
• Github syntax highlighting: Get syntax highlighting for LiveScript on GitHub #39, Add LiveScript support. github-linguist/linguist#183
• Rename NPM package 'LiveScript' to 'livescript': Rename NPM package 'LiveScript' to 'livescript' #261
• Add Livescript to CDNJS: Add LiveScript to cdnjs #240
• Add Prelude.ls to CDNJS: add prelude.ls to cdnjs prelude-ls#40

Bugs and Issues

Blocking

• None

Major

• None

Minor

• None

[neersighted]

@gkz Please feel free to edit this!

[vendethiel]

All of this isn't especially waiting for lsredux (afaik), since csredux isn't even finished yet. Feel free to comment #225, #109 is packed with callable binary logics (and working). Still waiting for syntax hl, no answer at all. Package renaming ... It's a bit too late, but why not for LS2.

[neersighted]

@Nami-Doc LS-Redux is LS2.

On another note, I had a long conversation with @gkz on IRC, I can paste the logs if you'd like.

[vendethiel]

Uh, yeah, I'm not talking about that. Ls2 being based on redux idea started (iirc) at the time the project was funded.
As for the rest, sure, paste. Can be interesting enough for me and others.

[gkz]

While this is nice, I think a better system to keep track of this is to use GitHub milestones with the appropriate issues. For now though, LS2 is at least a couple of months off from being started so I don't think it will be necessary yet, having things tagged as LS2 is sufficient. Thanks for the effort in putting this together though!