Jerry Shea
Jerry Shea
There are a few obvious gaps here - of particular concern is gaps in readingDocument0 and associated methods
These descend from the same base class but have subtly different behaviour (re-entrancy and PID vs PID+TID). Given the importance of locking to system stability, I feel there is benefit...
`[ERROR] /home/teamcity/agents/dev11b/work/39269a5b52212c57/target/generated-sources/annotations/net/openhft/chronicle/map/impl/CompiledMapQueryContext.java:[21,35] expected` Not at all clear why this happens
As it has been replaced for a year now
These are [mentioned in the docs](https://github.com/OpenHFT/Chronicle-Wire#example-with-methodreaders), but not explained at a high level together with their benefits (not least ease of use). We should at least link to some simpler...
Explain the different values of `net.openhft.chronicle.wire.WireType` and the different features/tradeoffs of each. Suggest we do this with a table of properties such as "self describing", "human readable", etc. As well...
If a tailer is at the start/end, and the first/last roll cycle is deleted, and you call tailer.toEnd again without refreshing the directory listing it remains at the non-existent index....