diff options
| author | Chuanqi Xu <yedeng.yd@linux.alibaba.com> | 2023-01-09 10:39:35 +0800 |
|---|---|---|
| committer | Chuanqi Xu <yedeng.yd@linux.alibaba.com> | 2023-01-09 10:40:23 +0800 |
| commit | ee1be282241b1253847e663af000f7082b7f03a3 (patch) | |
| tree | 4c16803cefd285f56811d00f6350600fbe934d22 /clang/lib/Basic/Module.cpp | |
| parent | 33794cffcfdadfffda2c78c73a25ce6fc58596f0 (diff) | |
| download | llvm-ee1be282241b1253847e663af000f7082b7f03a3.zip llvm-ee1be282241b1253847e663af000f7082b7f03a3.tar.gz llvm-ee1be282241b1253847e663af000f7082b7f03a3.tar.bz2 | |
[C++20] [Modules] Make placement allocation functions always visible
Close https://github.com/llvm/llvm-project/issues/59601.
This is actually a workaround for the issue. See the comments and the
test for example. The proper fix should make the placement allocation
functions acceptable based on the context. But it is harder and more
complex on the one side. On the other side, such workaround won't be too
bad in practice since users rarely call the placement allocation
functions directly.
So personally I prefer to address such problems in the simpler way.
Reviewed By: royjacobson
Differential Revision: https://reviews.llvm.org/D141023
Diffstat (limited to 'clang/lib/Basic/Module.cpp')
0 files changed, 0 insertions, 0 deletions