From 7fe552931a6894528b9c08095805172bf16cdec2 Mon Sep 17 00:00:00 2001 From: stephen-hero <78870893+stephen-hero@users.noreply.github.com> Date: Sat, 23 Dec 2023 00:04:28 +0200 Subject: [PATCH] Update task.md language in hints checked --- aliasServer/aliasServerUtil/task.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/aliasServer/aliasServerUtil/task.md b/aliasServer/aliasServerUtil/task.md index 6c152c68..15b13ed8 100644 --- a/aliasServer/aliasServerUtil/task.md +++ b/aliasServer/aliasServerUtil/task.md @@ -18,31 +18,31 @@ If you have any difficulties, **hints will help you solve this task**. ### Hints -
+
-Sometimes, type aliases are used in cases where there is no certainty that -the type used will not be replaced in the future. +Sometimes, type aliases are used in cases where there is uncertainty that +the type being used will not be replaced in the future. -For example, right now, we use the `Int` type as the `Identifier`, -but in the future, we can create our own class. -Using a type alias in this case will help us make this change as painless as possible in the future. +For example, right now, we're using the `Int` type as the `Identifier`. +However, in the future, we may create our own class. +Using a type alias in this case can help us make such a change as seamless as possible in the future.
-The property `counter` stores some internal information about the current state of the class instance. -So, the best way is to mark it as a private property to forbid access outside the class. +The `counter` property stores internal information about the current state of the class instance. +So, it's best to mark it as a private property to prevent access outside the class. -A simple example of why it is bad to use a `public` modifier here is that in such a -case, the user would be able to change the value of the `counter` property on their own -and we cannot guarantee its uniqueness. +A simple example of why it is bad to use a `public` modifier here is that, in such a +case, the user could independently change the value of the `counter` property, +compromising its uniqueness.
-It is better to set the value `0` as the default value for the property `counter`. +It is better to set `0` as the default value for the `counter` property. This makes it easier to create an instance of the class, -since you do not have to write the start value each time: +since you won't need to specify the starting value each time: ```kotlin val id = IdentifierFactory(0) @@ -57,7 +57,7 @@ Compare with:
-
+
Since the `uniqueIdentifier` function is so short, we can use the short notation: