Samuel Goto wrote: > (a) I did start the process within my company to apply the appropriate open source licenses to my JS verifier. It takes some time, but should be fine. I'll report back.
Sorry, I wouldn't have requested this if I'd known it wasn't your IP and there'd be a process to go through. But perhaps it is worth testing the process to see what happens if you've never tried it before. In the meantime I suggest marking any package.json in public repositories with "private": true, just so there's no doubt over the status of the code you're sharing. So you've got one of those programming gigs that allows you to work on whatever project you like on certain days (every Friday is usually cited as an example)? Nice! How do I land one of those? ;-) > (b) I did manage to make my parser and lexer streamable [1] (I rewrote the lexer as a state machine), which is good, but it made it substantially slower (I used async/await in JS which I think creates a Promise for every single token -- which likely is too much for set.mm's MB file), which is bad. I have something else in mind that I wanted to try, which is different than making the parser/lexer streamable, so I'll have to report back on this too. Yes, I've tried awaiting every single token in set.mm and it reduced my performance three-fold. https://groups.google.com/g/metamath/c/mFrNOFa7n8c/m/HkYkyJMaBAAJ My prefered solution is still a Nearley parser because then it owns a bunch of concerns that I don't think are particularly straightforward to deal with (but if that's the challenge you want, then hey, you've already written a working recursive descent parser). I know you abandoned your Nearley parser, but if you point it at demo0.mm rather than set.mm, I think you'll see the problem is that it's not generating any parser.results. I think trying to handle something it considers ambiguous is what ultimately leads to it running out of memory on larger files. I'm still hoping I can figure out how to use Glauco's parser, but I realise I've been frittering away my spare time writing docker containers full of metamath command line tools, and working through David A Wheeler's video in mmj2 and yamma as Glauco recommended, instead. However, I do intend to be back on the parse issue that's perhaps become a bit of a blocker for both of us, soon. Best regards, Antony -- You received this message because you are subscribed to the Google Groups "Metamath" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/metamath/CAJ48g%2BBgsTmnKiDRyH-1VCjrn7PUw%2BAca7%3DC9x_cfecsn59hgg%40mail.gmail.com.
