You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would write all allocations and frees into a buffer that we periodically flush to a file. When people report a bug, they could enable this feature, and provide their log.
Motivation
Easier to file bugs. Easier to reproduce bugs. Therefore, easier to fix bugs.
Details
Behind a cargo feature.
I guess we could use std::io::BufWriter, and say that this feature requires std
Ideally this would use the same operation definitions in ./test, so we could trivially turn them into regression tests. Also, shrink them to get reduced test cases.
The text was updated successfully, but these errors were encountered:
hi @fitzgen I would like to try this one. I don't know if this lib is still mantained and actively updated. Or there are any alternatives that made this lib obsolete. But if this lib is still up to date and you're mantaining it, I would like to help! And also learn, why not 😅
I'm not sure whether @joaolucasl is still developing this. But I guess not. So if it's ok for you @fitzgen I'll give it a try!
Summary
We would write all allocations and frees into a buffer that we periodically flush to a file. When people report a bug, they could enable this feature, and provide their log.
Motivation
Easier to file bugs. Easier to reproduce bugs. Therefore, easier to fix bugs.
Details
Behind a cargo feature.
I guess we could use
std::io::BufWriter
, and say that this feature requiresstd
Ideally this would use the same operation definitions in
./test
, so we could trivially turn them into regression tests. Also, shrink them to get reduced test cases.The text was updated successfully, but these errors were encountered: