Colin Eberhardt

https://github.com/ColinEberhardt/assemblyscript-regex/blob/main/.prettierignore it would be good to find a fix / workaround for this.

There are a few features not yet supported (e.g. negative lookahead). It would be useful to add these to the parser, but fail visibly when converting to an NFA.

See https://github.com/ColinEberhardt/assemblyscript-regex/pull/35 I haven't taken a terribly structured approach to error handling, hence there may be cases where the error reporting is poor or the behaviour unexpected. Furthermore, the [test...

Run the unit tests in TypeScript mode as well as WebAssembly / AssemblyScript

1

In order to ease development I'd like to always ensure that this project works equally well as TypeScript. A good way to ensure this is to ruin the unit tests...

NFA includes some states that are redundant

1


Strategy for ensuring functional correctness?

4

I'd consider this library to be a useable POC (proof of concept) in its current state. The implementation is based around the description of regex as provided by the [MDN...

Add CI tests

1

Add CI tests that ensure: - [x] unit tests all pass - [x] code is correctly formatted - [ ] the code can be executed both as AS and TS

Make this a TC39 proposal

4

I was looking at using Decorators to create some metadata-driven functionality, which is how I came upon this project. I'm surprised that this isn't on the list of TC39 proposals:...

Question: Does this action support alerts on pull requests?

18

I've successfully configured this action and everything is running very nicely on the `main` branch. I'm keen to also run this action on pull requests and receive alerts when there...

cannot declare an 'expect' within an arrow function that lacks parens

3

This works: ``` it("date.toString() is 1976-11-18", () => { expect(date.toString()).toBe("1976-11-18") }); ``` However, this fails with a compilation error: ``` it("date.toString() is 1976-11-18", () => expect(date.toString()).toBe("1976-11-18")); ```