Author here. The library is a toy project, it's far from being complete. Many things including macros are missing. Implementation style is derived from ClojureScript's compiler
It may be a toy, but I've been looking at doing very similar things at work. We have an optimizing compiler for spreadsheets, and many of the better optimizations are implemented as clojure syntax transforms (since Clojure was our first working target), so lowering that representation rather than selecting another is an attractive option, especially when compared to (for example) generating LLVM IR or code for some high level language.
What is even a compiler for spreadsheets? In spreadsheets you still have an AST, or is it a different structure? Is there any fundamental property of spreadsheet code that enables specific optimizations?
It's more that it necessitates certain optimizations, rather than enabling them.
You need to figure out how and when to merge expressions, when it's worth it to extract a loop where the same expression needs to be compiled as two or three variants, because there are invariants between all but two or three of the invocations. You also must decide which collections you want to create out of the reference soup, when you can alias/discard collections and values, how to hoist predicates (for IF and SWITCH), when you can avoid type coercion. For small workbooks, just using tagged unions in a 2D array, plus a string pool, will suffice, but our sheets are so big that we can't afford that.
This looks great! Thanks for building it. Any plans on adding support for Collections and their functions? If that were to be added, I'd have a lot of use cases for this library already.
Does the order of the sections matter in the text format?
Been poking a bit here and there at a wasm binary parser and know in that format they're supposed be in order (with custom sections sprinkled wherever) but can't recall seeing anything about the text format order.
The first error might be platform security limitation and the second one looks like a bug. Please file an issue on GitHub https://github.com/replete-repl (use repo for iOS or Android app)
Indeed Atom has problems, but it is still the most popular editor in JavaScript community.
I'm using it everyday for almost two years already and I'm happy with it. However that's my personal choice.
I created this small utility tool for myself, because it's extremely boring to translate HTML markup into React components. A good fit to use it when you starting a project with some designs. It will save you a couple of hours.
This is a small tool which I've created after constant boredom of moving markup from HTML documents into React components, when translating new designs into the app. For more or less complex structure it takes me usually half an hour to translate HTML from document into React components. Now I need less then 5 minutes to figure out components in the markup, annotate them and execute a command to get everything done.
This repo is describing Grunt-based dev environment. I'm just looking for tools that can be helpful in automation of processes. The most interesting part for me here are Testing & Metrics tools. Some great, but still not widely adopted, things like: Accessibility testing, Visual regression testing, Code complexity metrics.
Looking forward to add more useful stuff. Suggestions and PRs are welcome.
