Simplifying the poisoning mechanism used in HotSpot

[Kim Barrett]

On 8/17/25 2:43 PM, Julian Waters wrote:
> [...] you couldn't control it, meaning there was no way to
> permit forbidden methods.

My recollection is that the problem is not that there's no way to permit
forbidden functions where needed in our code, it's that there's no way to turn
off the forbidding for third party code (such as the gtest framework).

If all HotSpot code were in a namespace, we could easily poison via non-usable
declarations within that namespace, without affecting third party code in
other namespaces (including the global namespace). (And also without affecting
our ability to escape out where needed.) But that's not a thing.