cgeo/c-geo-opensource — comment on commit 8379a7a785be07298b7fb3da3f89736d133551dc
File:  line 0
By Bananeweizen:

The parse result loads all it contained caches directly from the database (and its logs, its waypoints, ...) when the parse result object is created. That is not necessary for offline lists, but causes a delay of half a minute for a list with 100 caches. I've only removed it for offline lists by now because I immediately noticed the delay there. I'm not sure whether or not it should also be changed for all the online searches.

To be honest, I didn't really understand why the ParseResult was introduced at all. For me it looked like the SearchResult should be enough for all the use cases, where one of those 2 classes might be needed, but I only did a very quick inspection yesterday.