Got an interesting issue for #regexp-tree: https://github.com/DmitrySoshnikov/regexp-tree/issues/179 … Let me know if you like source code transformation, compilers/transpilers, unicode, regexp, and would like to work on it.
-
-
@mathias, what we could share is the data itself probably. Re: the transpiler itself, parser, and other dependencies -- there is no need to mix two implementations. We can extract the data (unicode tables, etc) from your implementation into a separate module probably. -
I think we could start from https://github.com/mathiasbynens/regenerate-unicode-properties … , which is a JavaScript friendly translation from PropList.txt in UCD tailored for https://github.com/tc39/proposal-regexp-unicode-property-escapes …. We don't have to create another module with subtly different translations.
- 10 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.
on this issue. I have contributed to Babel and an ESLint plugin before and fans of Unicode things. I am comfortable on code transformer but I am new to RegExp and Automata. I would be great if you could mentor me on the design phase.