[blobfs][writeback] Use composition of WriteTxn instead of inheritance
Although slightly more verbose, being explicit makes the semantics of WritebackWork easier to reason about (and easier to refactor). Change-Id: If9b6bb6677eb3ec3713a31ef3eb03557c71685a2
Showing
- zircon/system/ulib/blobfs/blobfs.cpp 9 additions, 7 deletionszircon/system/ulib/blobfs/blobfs.cpp
- zircon/system/ulib/blobfs/include/blobfs/write-txn.h 0 additions, 1 deletionzircon/system/ulib/blobfs/include/blobfs/write-txn.h
- zircon/system/ulib/blobfs/include/blobfs/writeback-work.h 4 additions, 2 deletionszircon/system/ulib/blobfs/include/blobfs/writeback-work.h
- zircon/system/ulib/blobfs/journal-entry.cpp 4 additions, 4 deletionszircon/system/ulib/blobfs/journal-entry.cpp
- zircon/system/ulib/blobfs/journal.cpp 15 additions, 13 deletionszircon/system/ulib/blobfs/journal.cpp
- zircon/system/ulib/blobfs/test/journal-test.cpp 2 additions, 2 deletionszircon/system/ulib/blobfs/test/journal-test.cpp
- zircon/system/ulib/blobfs/writeback-queue.cpp 6 additions, 6 deletionszircon/system/ulib/blobfs/writeback-queue.cpp
- zircon/system/ulib/blobfs/writeback-work.cpp 3 additions, 3 deletionszircon/system/ulib/blobfs/writeback-work.cpp
- zircon/system/ulib/blobfs/writeback.cpp 2 additions, 2 deletionszircon/system/ulib/blobfs/writeback.cpp
Loading
Please register or sign in to comment