Replaced incorrect structs with classes in: "less far behind" than structs in record features
This commit is contained in:
NetMage 2020-09-10 21:56:10 -04:00 коммит произвёл GitHub
Родитель 1b48340ac8
Коммит 8cb28ad560
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 1 добавлений и 1 удалений

Просмотреть файл

@ -33,7 +33,7 @@ record struct Point(int X, int Y);
On the other hand, we could improve the performance of equality, completely separate from records.
For instance, the compiler could add equality methods if they are not present. We also do not necessarily
need to address structs first. Since structs already have many features of records they are, in a sense,
"less far behind" than structs in record features. It makes sense to concentrate first on classes and
"less far behind" than classes in record features. It makes sense to concentrate first on classes and
consider augmentations for structs in a future update.
So to return to the original question, we have to decide if we want to move forward with option (2), which