Alex Engelberg

Results 24 comments of Alex Engelberg

The first two are okay to me, the last one is another one I'd like to prohibit. Essentially, the style of "lone parens", either open ones with no text after...

I just now found the section about [trailing parens](https://github.com/bbatsov/clojure-style-guide#gather-trailing-parens), so the only thing it's missing is the part about opening parens followed by newlines. I agree with your point about...

Hi Zack, This is a really cool idea. Ever since your initial post several days ago I've been working on a way to generalize this type of problem. It's not...

https://github.com/aengelberg/instagenerate Presenting "instagenerate", a core.logic implementation of instaparse that can be used to generate inputs to parsers, and more. I think this has the potential to be very useful. --Alex...

I've thought about regular expressions a bit, and one thing I'm not sure how to handle is greedy vs non-greedy regular expressions. In instaparse, "#'a+' 'a'+" will always parse via...

@steinarvk There is now a LICENSE file in this repository.

I experimented by compiling the test runner in the instaparse project under the following conditions: * don't even compile instaparse source files = 257KB * `(:require [instaparse.core])` = 392KB *...

I don't really understand what's significantly different about the AOT'd version. There's something big I must be missing with regards to the assumptions made in the Instaparse code and how...

One idea: in EBNF syntax, allow rules to be namespaced with a dot separator, which get converted to namespaced keywords for hiccup. ``` myns.S = 'a' ``` Parse tree: ```...

A few things I noticed: 1. You need `\x{123456}` instead of `\u123456` for Unicode code points that aren't 4 digits. 2. Make sure you know how many backslashes you want...