Attention is currently required from: Edward O'Callaghan, Angel Pons, Daniel Campello, Anastasia Klimchuk, Peter Marheine.

View Change

1 comment:

• File layout.c:

  • Patch Set #5, 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.

To view, visit change 33543. To unsubscribe, or for help writing mail filters, visit settings.