src: add missing #include <unicode/ustring.h>#11754
Conversation
|
this fixes the node side. v8 side will have to be done upstream |
TimothyGu
left a comment
There was a problem hiding this comment.
Would be best if the commit message specifies which functions in ustring.h we are using right now.
|
@TimothyGu good idea, will do |
b013aa2 to
0543a78
Compare
|
@TimothyGu please re review |
|
v8 issue will be fixed in https://codereview.chromium.org/2738503008 (work in progress) It may be that other changes are needed as well, but this gets the immediate one. |
0543a78 to
4fb149d
Compare
4fb149d to
5efb15e
Compare
* We use these functions that are declared in <unicode/ustring.h>
u_strFromUTF8()
u_strToUTF8()
* At present, <unicode/ustring.h> is indirectly included, but this will
likely change in future ICUs. Adding this header has been the right
thing to do for many years, so it is backwards compatible.
Fixes: nodejs#11753
PR-URL: nodejs#11754
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Timothy Gu <[email protected]>
* We use these functions that are declared in <unicode/ustring.h>
u_strFromUTF8()
u_strToUTF8()
* At present, <unicode/ustring.h> is indirectly included, but this will
likely change in future ICUs. Adding this header has been the right
thing to do for many years, so it is backwards compatible.
Fixes: nodejs#11753
PR-URL: nodejs#11754
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Timothy Gu <[email protected]>
|
@srl295 should this be backported to v6.x? |
|
ping |
|
@MylesBorins If the patch applies, it doesn't hurt to backport it. It improves future proofing if someone were to use a later ICU with v6.x. Short answer, yes I think it should be. |
|
@srl295 it doesn't land cleanly, please feel free to backport |
Fixes: #11753
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
i18n