At least for class 'OsuDb', many osuers have a large 'osu!.db' file which contains a huge amount of beatmaps. I think there is a better way to handle this since current solution will leads to high memory usage and extremely GC call. Comparing to do things after reading the whole file, I prefer to handle things while reading, and not store the previous object after each enumeration (Users can store it manually).
At least for class 'OsuDb', many osuers have a large 'osu!.db' file which contains a huge amount of beatmaps. I think there is a better way to handle this since current solution will leads to high memory usage and extremely GC call. Comparing to do things after reading the whole file, I prefer to handle things while reading, and not store the previous object after each enumeration (Users can store it manually).