pennae 8775be3393 store Symbols in a table as well, like positions ... this slightly increases the amount of memory used for any given symbol, but this increase is more than made up for if the symbol is referenced more than once in the EvalState that holds it. on average every symbol should be referenced at least twice (once to introduce a binding, once to use it), so we expect no increase in memory on average. symbol tables are limited to 2³² entries like position tables, and similar arguments apply to why overflow is not likely: 2³² symbols would require as many string instances (at 24 bytes each) and map entries (at 24 bytes or more each, assuming that the map holds on average at most one item per bucket as the docs say). a full symbol table would require at least 192GB of memory just for symbols, which is well out of reach. (an ofborg eval of nixpks today creates less than a million symbols!)		2022-04-21 21:56:31 +02:00
..
context.cc	store Symbols in a table as well, like positions	2022-04-21 21:56:31 +02:00
derivation.nix	Remove corepkgs/derivation.nix	2020-09-17 09:41:02 +02:00
fetchClosure.cc	store Symbols in a table as well, like positions	2022-04-21 21:56:31 +02:00
fetchMercurial.cc	store Symbols in a table as well, like positions	2022-04-21 21:56:31 +02:00
fetchTree.cc	store Symbols in a table as well, like positions	2022-04-21 21:56:31 +02:00
fromTOML.cc	replace most Pos objects/ptrs with indexes into a position table	2022-04-21 21:46:06 +02:00