iu-parfunc / tslogger

thread-safe logging

tslogger

Thread-safe logging for concurrent Haskell programs.

tslogger's Issues

Add tests that verify fuzz-testing capability is still working

This worked in LVish, but it should be tested as part of the suite for this package.

This depends on #1 of course.

@peter-fogg, this is just what we discussed before.

Set up Travis and Jenkins testing

For this package alone, not just as part of LVish.

Schedule Fuzz testing -- factor out a library of memory operations

Code that uses the logging framework currently, looks something like this:

  do ...
     log "About to operate on memory"
     casIORef ...
     log "About to read from memory..."
     readIORef ...

Etc. The point is, as the data structure author you need to remember to call a log command before any operation that peeks or pokes at memory. In fuzz testing / model checking mode, the log command is what actually blocks, gating execution until the scheduler decides that, say, the casIORef operation above is allowed to proceed, at which point it unblocks long enough to perform one memory operation, sequentially.

But this is tedious! We should abstract out a library of procedures like casIORef which automatically call log before doing the memory operation. This will mean that the data structure author simply needs to switch their imports from Data.IORef and Data.Atomics, to their replacement modules.