Why ExecutionAndPublication and PublicationOnly have such names?

[MNF]

Could you please explain in the article, why ExecutionAndPublication and PublicationOnly have such names? The descriptions of modes do not mention publication and it is not clear how behavior is associated with the name of mode.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: c082508c-af74-1d6a-a954-e70aca02e1a4
• Version Independent ID: 85c92c40-9a7a-cd0f-fa63-53c87cb5febe
• Content: Lazy Initialization
• Content Source: docs/framework/performance/lazy-initialization.md
• Product: dotnet-framework
• GitHub Login: @rpetrusha
• Microsoft Alias: ronpet

[mairaw]

@kouvel can you help with this question? Is this an issue with the docs?

[kouvel]

I suspect that it's referring to what guarantees are made. There's some code that would do initialization and then a value produced would be published to be used by consumers thereafter. Sort of like:

• A safety mode of None does not guarantee anything (not to be used by multiple threads I figure, since otherwise multiple initializations may occur and multiple values may be published and used by consumers)
• A safety mode of Publication would guarantee that exactly one result of an initialization would be published and used by consumers, but does not guarantee that initialization code only runs once nor that it may not run concurrently
• A safety mode of ExecutionAndPublication would guarantee that initialization code would run in a thread-safe manner, and only one initialization would occur, the result of which would be published and used by consumers

[dotnet-bot]

This issue has been closed as part of the issue backlog grooming process outlined in #22351.

That automated process may have closed some issues that should be addressed. If you think this is one of them, reopen it with a comment explaining why. Tag the @dotnet/docs team for visibility.

[MNF]

@dotnet/docs, will @kouvel’ s explanation above be useful to include in the documentation?

[kouvel]

Yes I'll add to the docs