GitLab

Not only is the code much cleaner, we also have the added advantage
of not spinning up new threads whenever we parse a new file.

Furthermore the signals have been cleaned up to remove the unsafe
accessal of the old ParseThread once it has finished parsing.

BUG: 316307

Never ever 'cache' the end iterator, as it might get invalidated
after a call to erase.

This fixes tooltips for more complicated function signatures

BUG: 305272

QRegExp is not thread safe, hence don't share it between
threads by making it static.

store labels on first encounter in a QHash and reuse copies of
the labels there, which are just shallow, implicitly shared copies.

further decreases the memory consumption considerably for my test case,
where the consumption goes down by about 50%.

Many thanks to André Wöbbeking for the suggestion.

CCMAIL: Woebbeking@kde.org

easier and faster this way

this is especially noticeable for large, compressed files
where loading easily takes a few seconds. now, instead
of hanging the UI we show a throbber progress bar. neat

not important, just to make it easier
to run memcheck on it later

we only convert to QString on demand when we actually display a string
to the user. most often, this is just a small subset of the data
we have lying around in total.

the memory consumption gain is esp. noticeable for big data files,
where it reduces the memory consumption by ~40%