Ján

> Perhaps that idea of `OS\` might be better under _Private or something. That sounds reasonable to me. What would be the disadvantages? Are there legitimate use-cases for people using...

Yeah I guess if one of the namespaces (OS?) is very explicitly for low-level things that almost no one needs, and anything that is not strictly equivalent to a low-level...

Sounds reasonable. Also eventually the OS namespace should probably be built-in, not part of HSL, right? We don't want wrappers like ``` namespace OS { function opendir($path) { return \opendir($path);...

> IMO ideally the whole HSL should be built-in :) I meant "built-in" as in written in C++ with Hack code only in .hhi files. I don't think we need...

This looks like a valid usecase to me, I agree we should support it somehow. I'm not sure we can commit to a specific API right now -- from what...

> How would you add more specs to the Config::TYPE_SPEC_CLASSES constant? Sorry that was a bad example, of course it can't be a constant, but probably some function that gets...

should we do this now?

Is this about https://github.com/hhvm/packaging/blob/master/aws/ondemand/facebook/hhvm/seccomp.json ? My intention with that was to make it less restrictive (I couldn't run HHVM tests without it), not more restrictive/secure (there's no reason for that...

I just copypasted that file from the first search result for the error message I was getting :P