https://github.com/staab/janet-js

A compiler written in janet, to compile (a subset of) janet to javascript.
https://github.com/staab/janet-js

Last synced: 1 day ago
JSON representation

A compiler written in janet, to compile (a subset of) janet to javascript.

• Host: GitHub
• URL: https://github.com/staab/janet-js
• Owner: staab
• License: mit
• Created: 2020-05-24T18:46:17.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2020-05-24T18:46:29.000Z (over 4 years ago)
• Last Synced: 2024-08-04T04:01:08.679Z (3 months ago)
• Language: JavaScript
• Homepage:
• Size: 57.6 KB
• Stars: 11
• Watchers: 4
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-janet - janet-js

README

        
# janet-js

A compiler written in janet, to compile (a subset of) janet to javascript.

# Design

I want to try something different from simple janet-embedded-in-js ala clojurescript. Close host interop, while convenient, messes with a lot of the semantics of the language. In my experience, Clojurescript loses:

- Arity checks

- Type errors

- Property access errors

- Semantic differences between strings and keywords

I love the way Janet provides an C api for language extension rather than host interop. The C API has some limitations, but within those you can add whatever functionality you want to the language, all behind the facade of an "abstract type". I'd like to do the same for javascript.

There are some tradeoffs here; it won't be possible to access window.whatever from janet-js, since I want to take a more sandboxed approach. This might mean heavier code to implement run-time checks of janet semantics, and more memory to maintain annotations of javascript objects to maintain semantics when crossing language barries.

As an example, instead of `(= "object" (type (:querySelector document "a")))`, I want the user to have to explicitly opt-in to native functionality, and have it exposed not as a DOMNode, but as a janet-js abstract type. See the example directory for more details.

## Notes

- Reconcile asynchrony models - threads, fibers, promises

- Use Object.freeze for immutability

- Maybe use Maps or WeakMaps or some dictionary implementation that can use something other than strings as keys

# Disclaimer

This is pre-alpha software. Please open an issue if you'd like to use it in a project.