On Sat, Feb 6, 2021 at 9:18 AM Nigel Tao <nigel...@golang.org> wrote:

> It doesn't have any in-memory representation of the not-frequently-used
> parts, including the actual glyph vectors.
>

Correction: it doesn't have not-frequently-used or too-big-to-cache parts,
and glyph vectors are the latter. Avoiding "takes double the memory" is
precisely the concern.

>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAOeFMNXPpVLPrSRrcQCw9UxxZHPghA%3DyqToMUv5ioh2x2h1JPg%40mail.gmail.com.

Reply via email to