> I don't really see the 4x factor increase, but actually a 1 to 1 mapping with
> my approach.
the 3X or 4X increase is in the C file generated, since it contains escape
sequences, eg:
STRING_LITERAL(TM__1m9cQUY9abSjxCA8ws9b1wH9ag_4, "\317\372\355\376\007\000\
Run
du -sh /Users/timothee/git_clone/nim/timn/build/nimcache/@mt12666b.nim.c
14M /Users/timothee/git_clone/nim/timn/build/nimcache/@mt12666b.nim.c
the object file and binary will be 5MB du -sh
/Users/timothee/git_clone/nim/timn/build/nimcache/@mt12666b.nim.c.o 4.9M
/Users/timothee/git_clone/nim/timn/build/nimcache/@mt12666b.nim.c.o
the fact that this approach requires encoding/decoding and blows up
intermediate size by 3-4X is not good if your embedded data is large (affects
memory, intermediate disk size and compile times);
the other approach i suggested didnt' have this problem
