purescript / gsoc Goto Github PK

Possible directions:

• Develop a tool for converting IDL files into PureScript FFI modules, using purescript-webidl.
  • Use your tool to improve the state of PureScript's HTML5 bindings.
• Develop a tool for creating succinct FFI specifications in YAML files, and converting those specifications into FFI modules.
• Develop a tool for generating .d.ts files from PureScript's externs files.

Possible directions:

• Survey the existing work on multiple backends (pure11, pure14, truffled-purescript, Lua, etc.)
• Extend/define appropriate ASTs to extract common features used during code generation
• Implement a new code generator or port an existing one to use your new machinery.
• Port some core libraries to a new backend, or implement a killer application for a new backend.

Possible directions:

• Design a PureScript library for generating code at compile time.
• Either:
  • Implement an interpreter for PureScript's functional core language.
  • Implement a bridge to allow psc to evaluate PureScript code using NodeJS during compilation.
• Use your interpreter and library to compile and run PureScript code at compile time.
• Demonstrate some application of Template PureScript:
  • Type-safe HTML templating
  • Type class deriving

Possible directions:

• Add syntax to instruct the compiler to inline a particular function.
• Implement inlining in the compiler at various points in the compilation pipeline.
• Update the core libraries to inline key functions.

Possible directions:

• Expand the support for browser-based evaluation, with support for things like canvas graphics, web audio, DOM manipulation, etc.
• Implement :load functionality.

Develop a source code formatting and highlighting tool:

• Create an AST for formatted PureScript source code.
• Implement one or more formatters: plain text, HTML, etc.
• Integrate your tool into Pursuit's "source" functionality.

Possible directions:

• Improve support for NPM packages.
• Enforce semantic versioning using the type system.