[libcxx-commits] [libcxx] Simplify the __assertion_handler build logic. Be friendly to IDEs. (PR #93333)

[Louis Dionne via libcxx-commits]

ldionne wrote:

Let's say you configure libc++ with a custom assertion handler. Will your IDE assume that `libcxx/include/__assertion_handler` is being used even though the configuration says otherwise?

If so, then isn't this the wrong way to fix this issue? Couldn't we instead teach the IDE what we're really doing? What IDE are you using, by the way?

https://github.com/llvm/llvm-project/pull/93333