[flashrom-gerrit] Change in flashrom[master]: layout: Introduce flashrom_layout_new()

[Nico Huber (Code Review)]

Attention is currently required from: Edward O'Callaghan, Angel Pons, Daniel Campello, Anastasia Klimchuk, Peter Marheine.
Nico Huber has posted comments on this change. ( https://review.coreboot.org/c/flashrom/+/33543 )

Change subject: layout: Introduce flashrom_layout_new()
......................................................................

Patch Set 7:

(1 comment)

File layout.c:

https://review.coreboot.org/c/flashrom/+/33543/comment/05012cdb_b4079b14 
PS5, Line 397: malloc
> It seems reasonable to be defensive here, to more predictably catch use of uninitialized entries.

I am not used to such errors, so I need much more details about
the expectations. How does it look like when you catch an unwanted
0-initialization? How is it better compared to some random value?
What is the expected effect on programming habits? For instance,
I'd expect people to be lulled in false confidence that things
are usually 0-initialized (instead of learning C semantics properly).
That's just an example; I'd need something that outweighs such
concerns, then I'd be happy to support this pattern.