MDS/openide
1
0
Fork 0
mirror of https://gitflic.ru/project/openide/openide.git synced 2025-12-14 18:05:27 +07:00
Code Issues Packages Projects Releases Wiki Activity

cleanup doc comment to make the method reference work

Browse Source 
GitOrigin-RevId: 77b9533fb95d385d2b6cc0677ee3d134120f255a
This commit is contained in:
Max Medvedev
2024-05-14 11:42:35 +02:00
committed by intellij-monorepo-bot
parent 53a577a12a
commit 04185d7432
1 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
platform/projectModel-impl/src/com/intellij/workspaceModel/ide/impl/WorkspaceModelImpl.kt
View File

@@ -50,15 +50,16 @@ open class WorkspaceModelImpl(private val project: Project, private val cs: Coro
final override val entityStorage: VersionedEntityStorageImpl
private val unloadedEntitiesStorage: VersionedEntityStorageImpl
// replay = 1 is needed to send the very first state when the subscription fo the flow happens.
// otherwise, the flow won't be emitted till the first update. Since we don't update the workspace model really often,
// this may cause some unwanted delays for subscribers.
// This is used in the [subscribe] method, where we send the first version of the storage
// right after the subscription.
// However, this means that this flow will keep two storages in the flow: the old and the new. This should be okay
// since the storage is an effective structure, however, if this causes memory problems, we can switch to
// replay = 0. In this case, no extra storage will be saved, but the event will be emitted after the first
// update of the WorkspaceModel, what is probably also okay.
/** replay = 1 is needed to send the very first state when the subscription fo the flow happens.
otherwise, the flow won't be emitted till the first update. Since we don't update the workspace model really often,
this may cause some unwanted delays for subscribers.
This is used in the [subscribe] method, where we send the first version of the storage
right after the subscription.
However, this means that this flow will keep two storages in the flow: the old and the new. This should be okay
since the storage is an effective structure, however, if this causes memory problems, we can switch to
replay = 0. In this case, no extra storage will be saved, but the event will be emitted after the first
update of the WorkspaceModel, what is probably also okay.
*/
private val updatesFlow = MutableSharedFlow<VersionedStorageChange>(replay = 1)
private val virtualFileManager: VirtualFileUrlManager = IdeVirtualFileUrlManagerImpl()