rewrite-clj

https://github.com/clj-commons/rewrite-clj
2019-04-11T00:01:33.021300Z

thanks for the clarification 🙂

2019-04-11T00:21:07.025300Z

i've re-read what i wrote earlier and am thinking it may be confusing. to clarify, what i am thinking is: at zipper creation time, specify what to skip (or not), this info gets stored along with (or in some sense as part of) the zipper. in the case of the custom zipper, since that's already a map, an obvious place to keep the info is as a key-value pair (possibly the value is a set or map). that info might then be consulted in places such as zip/whitespace.clj to determine what to skip. one specific place is in skip-whitespace's second arity, where there is a use of whitespace-or-comment?.

borkdude 2019-04-11T09:36:29.026400Z

if I would fork rewrite-clj because I only need the parser bits and I would like to tweak those for my own use, what should I do LICENSE-wise? not planning this right now, but I might in the future

lread 2019-04-11T10:08:49.032500Z

Don’t know, but when the original author of rewrite-cljs took work from rewrite-clj, he left the original LICENSE and added his own LICENSE. Under clj-commons we are just going to leave both licenses as is for rewrite-cljs.

borkdude 2019-04-11T10:12:07.032900Z

I’ll consult the original author before doing so

lread 2019-04-11T10:13:00.033400Z

Yeah, that would be best.