https://bugs.kde.org/show_bug.cgi?id=374097
--- Comment #18 from Sven Brauch <m...@svenbrauch.de> --- Git commit 4cf23720b123dee3b4ad85957ed165d23e37e1e7 by Sven Brauch. Committed on 14/01/2017 at 12:15. Pushed by brauch into branch '5.1'. container types: do not write lock when calling addContentType() This should be done from outside. Rationale: In many cases (see e.g. kdev-python expression visitor) the type is instantiated, a lot of content types are added, and only then is it attached to a declaration. In this case, no write locking is necessary, and it prevents the calling code to hold a more coarse-scale read lock. This requires changes to the code using the API only if the modified type is already accessible through a declaration. I changed kdev-python and checked kdev-ruby (it has no cases where this applies and no read-lock is held at that time); kdev-php doesn't use this class. M +3 -1 language/duchain/types/containertypes.h https://commits.kde.org/kdevplatform/4cf23720b123dee3b4ad85957ed165d23e37e1e7 -- You are receiving this mail because: You are watching all bug changes.
