Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix statics.md #355

Open
wants to merge 1 commit into
base: statics
Choose a base branch
from
Open

Fix statics.md #355

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion proposals/statics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1967,7 +1967,7 @@ performance is a secondary concern, if a concern at all. For performance-sensiti
opt-in capabilities to be used by experts who write performance-sensitive code. One such performance-oriented
capability is a `value class`, and another such performance-oriented capability is a `static object`.
They take away performance-affecting "provides a stable reference" feature of classes and objects respectively
for those cases where you can do away without it. If you take legal Kotlin code and replace `value class` with `class`
for those cases where you can do away without it. If you take legal Kotlin code and replace `value class` with `data class`
and `static object` with `object` the code will mostly compile and work as before
(maybe with few non-essential differences), but will lose some efficiency.

Expand Down