| OLD | NEW |
| (Empty) | |
| 1 # platform/newwtf (will become platform/wtf eventually) |
| 2 |
| 3 This is a temporary location where all files under Source/wtf/ will be moved |
| 4 eventually. For details about WTF relocation project, see |
| 5 [the proposal](https://docs.google.com/document/d/1shS1IZe__auYxjm9FhPbTY2P01FbN
TMYRh-nen5gkDo/edit?usp=sharing) |
| 6 and |
| 7 [the design doc](https://docs.google.com/document/d/1JK26H-1-cD9-s9QLvEfY55H2kgS
xRFNPLfjs049Us5w/edit?usp=sharing). |
| 8 You can see |
| 9 [bug 691465](https://bugs.chromium.org/p/chromium/issues/detail?id=691465) |
| 10 for the project's status. |
| 11 |
| 12 During the project, files in wtf/ are moved to platform/newwtf/ incrementally, |
| 13 and redirection headers will be placed in wtf/. So nothing should break in the |
| 14 meantime. You can continue including WTF headers like `#include "wtf/Xxx.h"` |
| 15 till the next announcement in blink-dev. |
| 16 |
| 17 Why "new" wtf? We initially named this directory platform/wtf/, but it turned |
| 18 out this would cause a warning on win-clang due to MSVC-specific #include |
| 19 search order. Basically, we can't have "platform/wtf/Foo.h" and "wtf/Foo.h" at |
| 20 the same time, since `#include "wtf/Foo.h"` may imply platform/wtf/Foo.h |
| 21 depending on the context. We don't want to turn off this warning Blink-wide, |
| 22 and that's why we have platform/newwtf/. |
| 23 |
| 24 platform/newwtf/ will be renamed to platform/wtf/ after we get rid of wtf/ |
| 25 completely. |
| OLD | NEW |