Logging seems to approximately double the size of the stack due to all the Display/Debug impls and string literals.
Logging should be opt-in via a log Cargo feature. This means we have to define our own logging macros that forward to the ones in log if the feature is enabled, and that expand to nothing if not.
Until rubble is split into a library, the feature can stay on by default to ease development.
Logging seems to approximately double the size of the stack due to all the
Display
/Debug
impls and string literals.Logging should be opt-in via a
log
Cargo feature. This means we have to define our own logging macros that forward to the ones inlog
if the feature is enabled, and that expand to nothing if not.Until
rubble
is split into a library, the feature can stay on by default to ease development.