[libcxx-commits] [PATCH] D139270: [libc++] Rename __tuple to __tuple2 to avoid file collision
Louis Dionne via Phabricator via libcxx-commits
libcxx-commits at lists.llvm.org
Mon Dec 5 05:48:52 PST 2022
ldionne added a comment.
>From the patch, I'm not sure I understand what's the process you are expecting us to follow for renaming a file to a directory. Are you suggesting that we rename it to `__tuple2` for some amount of time (how long?) and then rename it back to `__tuple`? Are you suggesting that we instead never reuse a name that has been used for a header in the past for a directory?
I know that renaming files to directories can cause issues, I myself have issues downstream because of this. But I think those are shortcomings of the systems we are using, and I have been unwilling to create complexity upstream because of that, so far. If this problem is shared by more than just me, it may be worth finding a solution for everyone, however never reusing a previous file name is not going to fly. I think the best we can do is probably wait for one release before doing the renaming back to `__tuple`.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D139270/new/
https://reviews.llvm.org/D139270
More information about the libcxx-commits
mailing list