diff options
author | Kartik K. Agaram <vc@akkartik.com> | 2016-04-28 17:23:50 -0700 |
---|---|---|
committer | Kartik K. Agaram <vc@akkartik.com> | 2016-04-28 17:36:30 -0700 |
commit | 7858a06a5444328594bac9a9213bcbdda20580d6 (patch) | |
tree | 7a3612d8d2388a966dc1e5162404922a227a8451 /arc/.traces/string-find-next-first | |
parent | 4f5bb5b6b199b9ccf1bf12082436d9f841559b2c (diff) | |
download | mu-7858a06a5444328594bac9a9213bcbdda20580d6.tar.gz |
2882 - warn if programmer overuses transform_all()
This continues a line of thought sparked in commit 2831. I spent a while trying to avoid calling size_of() at transform-time, but there's no getting around the fact that translating names to addresses requires knowing how much space they need. This raised the question of what happens if the size of a container changes after a recipe using it is already transformed. I could go down the road of trying to detect such situations and redoing work, but that massively goes against the grain of my original design, which assumed that recipes don't get repeatedly transformed. Even though we call transform_all() in every test, in a non-testing run we should be loading all code and calling transform_all() just once to 'freeze-dry' everything. But even if we don't want to support multiple transforms it's worth checking that they don't occur. This commit does so in just one situation. There are likely others.
Diffstat (limited to 'arc/.traces/string-find-next-first')
0 files changed, 0 insertions, 0 deletions