Vicent Martí

Hi @skant7! As explained in the description, implementing all the missing functionality in the evalengine during your internship is unfeasible, so as part of your application you should come up...

@Weijun-H: good catch! The bitwise functions were already implemented but we didn't update the issue. I've ticked their boxes -- I don't think any further work needs to be done...

Hey @crsdvaibhav! This was a GSoC'22 project that has already finished. We still don't know whether Vitess will participate in GSoC'23, whether it'll get accepted, and whether this project will...

Hey @Anu-Ra-g! I am going very soon on paternity leave (:baby: :tada:) so there isn't going to be any `evalengine` related projects for Vitess this year, as I won't be...

Hey, although I've dropped support for Python on the library (as you can read on the README file), here's some ideas to get this fixed: this is an issue with...

The finalizers approach is IMO out of the question because they perform horribly in Go. I do agree this is a bit of a footgun in the pooling API, and...

Wow, I totally overlooked all the +1s. Fine, footnotes seem by far the least intrusive of the PHP Markdown extensions. Let me look into them.

I'm hoarded atm. I'd _really_ _really_ appreciate if somebody stoop up and opened a PR for this. I'll gladly give implementation advice.

@jmendeth's summary is pretty accurate. We shipped a replacement parser as part of CommonMark, which should hopefully fit your needs if you're looking for a C library to parse Markdown.

Yes, this is certainly an interesting corner case. I'll try to handle it more gracefully.