diff options
| author | Vsevolod Tolstopyatov <qwwdfsad@gmail.com> | 2023-08-14 19:45:32 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-08-14 19:45:32 +0200 |
| commit | 2269ac5e003b1cce90742b5f5ed9cd294dd099f4 (patch) | |
| tree | b90bdab54c9ce0b144ed4485905e5257f174a58b /integration-tests/gradle/projects/serialization/template.settings.gradle.kts | |
| parent | 2fd8e9096706545f8b77e1e66bcc876d7e29f82c (diff) | |
| download | dokka-2269ac5e003b1cce90742b5f5ed9cd294dd099f4.tar.gz dokka-2269ac5e003b1cce90742b5f5ed9cd294dd099f4.tar.bz2 dokka-2269ac5e003b1cce90742b5f5ed9cd294dd099f4.zip | |
Refactor and document DisplaySourceSet, deprecate SelfRepresentingSingletonSet (#3105)
* Deprecate internal API SelfRepresentingSingletonSet for removal as being harmful and unimplement it in DisplaySourceSet
* Provide no automatic migration for DisplaySourceSet, as there are no mechanisms for that. Manual migration is the replacement of 'dss' to `setOf(dss)` where applicable
* Introduce a convenience-member DefaultRenderer.buildContentNode to avoid wrapping DSS into set manually
* Document DisplaySourceSet
* Replace Iterable<DisplaySourceSet>.sourceSetIDs with more straightforward Iterable<DisplaySourceSet>.computeSourceSetIds(), refactor all the usages, save some allocations
* Start caching CompositeSourceSetID properties to avoid excessive allocations
* Update integration tests on the latest revision with Knit version where the workaround is applied
Fixes #2897
Diffstat (limited to 'integration-tests/gradle/projects/serialization/template.settings.gradle.kts')
0 files changed, 0 insertions, 0 deletions