Add support for ICU

[kitsonk]

We should add ICU to rusty_v8 in some fashion.

[flying-sheep]

Since ICU is large (as discussed in the linked issue): It would be great if choosing between static and dynamic linking is possible. On my system, all those projects link to ICU, and it would be nice to not have a second copy of it embedded in deno.

• bind boost-libs calibre chromium dotnet-runtime harfbuzz-icu haskell-text-icu lib32-icu libcdr libical libmspub libreoffice-fresh libvisio libxml2 nodejs nuspell postgresql powershell r raptor smbclient texlive tracker3 xfsprogs

Of course only if it’s feasible. I speculate that ICU is much more stable than V8, so dynamically linking the former is probably much more realistic than with the latter (without things breaking and having to be rebuilt all the time)

[bnoordhuis]

@flying-sheep That's probably out of the question because V8 is only tested against a particular build of ICU - the fork that Chromium bundles - and we don't have the resources to test against other versions or builds.

Here are file sizes:

$ ls -lh lib*icu*.a | awk '{print $5 " " $9}'
19M libicuucx.a
43M libicui18n.a
27M libicudata.a

The first two contain code, where you only pay for what you use. I expect that V8 pulls in a few MB, I remember that was what it amounted to in Node.js.

The last file is the big data table ICU uses. rusty_v8 can either embed it or load it externally so it can be shared but deno probably wants to embed it.

Node.js used to ship a stripped down table containing only en_US but they (we - I was involved in that decision) stopped doing that in v14. I don't plan on revisiting that for rusty_v8 or deno.

[bnoordhuis]

Closing, done.

[waldyrious]

done.

Just for the record, it appears that the main PR for this was #603.