Siddhesh Poyarekar

Yeah those are only a subset of the extensions that I thought were safe enough (i.e. won't collide with the namespace of future lua features) to incorporate without the flag....

I didn't see this with my fork, I'll check with openresty and report back.

OK, so I don't see this because the misc/* tests are not run by default by the test.lua setup. I need to fix that. Meanwhile, I ran the tests individually...

It appears that the current state is the following: * The `-fvtable-verify` option was implemented long ago with the idea that it may be useful, but never got any use...

Analyzer options are not suitable for default use even though we try to keep false positives/negatives down, but it would be great to have a section on analyzer (or even...

> Since this document is more about security and memory saftey IDK if it should go too deep into "general code quality" if thats' what a lot of the analyze...

We added it under the impression that it's the libc++ equivalent of `_GLIBCXX_ASSERTIONS` (https://github.com/ossf/wg-best-practices-os-developers/pull/128 for context) but evidently, it's not a documented feature. I'm in favour of dropping it until...

It's a debug flag, so I'm not sure if it's suitable for this guide, which intends to document flags for use in production. It would be nice to have a...

I don't want to promise (because this is largely going to be free time work for me and it's summer!) but I can take a stab at it at some...

I can't attend tomorrow's call due to a conflict, but I wanted to share that I've started working on this, here's a preview: https://github.com/siddhesh/wg-best-practices-os-developers/commit/fc1dce2742d0ff049a3e5b73817b96c3ab740acd I'll send a PR once I...