Attention is currently required from: Aarya, Anastasia Klimchuk, Bill XIE.

View Change

1 comment:

• Patchset:

  • Patch Set #1:

    Thank you for context! This was very educational, I understand now. […]

    I think minimizing the number of bytes erased ("safe") is the correct default behavior, regardless. A command-line option to instead reduce the number of erases ("quick-n-dangerous", assumed to operate faster but wear flash faster) might be nice, though.

    Making that a compile-time option seems like it's easy for a user to configure it to be quick-n-dangerous then unintentionally use that mode later, whereas requiring quick-n-dangerous mode to be opt-in for each invocation (default to safe operation) should prevent any surprises. The choice could also be easily exposed to library users then, too.

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