pennae 6526d1676b replace most Pos objects/ptrs with indexes into a position table ... Pos objects are somewhat wasteful as they duplicate the origin file name and input type for each object. on files that produce more than one Pos when parsed this a sizeable waste of memory (one pointer per Pos). the same goes for ptr<Pos> on 64 bit machines: parsing enough source to require 8 bytes to locate a position would need at least 8GB of input and 64GB of expression memory. it's not likely that we'll hit that any time soon, so we can use a uint32_t index to locate positions instead.		2022-04-21 21:46:06 +02:00
..
context.cc	replace most Pos objects/ptrs with indexes into a position table	2022-04-21 21:46:06 +02:00
derivation.nix	Remove corepkgs/derivation.nix	2020-09-17 09:41:02 +02:00
fetchClosure.cc	replace most Pos objects/ptrs with indexes into a position table	2022-04-21 21:46:06 +02:00
fetchMercurial.cc	replace most Pos objects/ptrs with indexes into a position table	2022-04-21 21:46:06 +02:00
fetchTree.cc	replace most Pos objects/ptrs with indexes into a position table	2022-04-21 21:46:06 +02:00
fromTOML.cc	replace most Pos objects/ptrs with indexes into a position table	2022-04-21 21:46:06 +02:00