kojiromike commented on code in PR #2448:
URL: https://github.com/apache/avro/pull/2448#discussion_r1297907053
##########
doc/content/en/docs/++version++/Specification/_index.md:
##########
@@ -180,9 +180,9 @@ For example, 16-byte quantity may be declared with:
```
### Names {#names}
-Record, enums and fixed are named types. Each has a fullname that is composed
of two parts; a name and a namespace, separated by a dot. Equality of names is
defined on the fullname.
+Record, enums and fixed are named types. Each has a fullname that is composed
of two parts; a name and a namespace, separated by a dot. Equality of names is
defined on the fullname: it is an error to specify two different types with the
same name.
-Record fields and enum symbols have names as well (but no namespace). Equality
of fields and enum symbols is defined on the name of the field/symbol within
its scope (the record/enum that defines it). Fields and enum symbols across
scopes are never equal.
+Record fields and enum symbols have names as well (but no namespace). Equality
of field names and enum symbols is defined within their scope (the record/enum
that defines them): it is an error to define multiple fields or enum symbols
with the same name in a single type. Fields and enum symbols across scopes are
never equal, so field names and enum symbols can be reused in a different type.
Review Comment:
```suggestion
Record fields and enum symbols have names as well (but no namespace).
Equality of field names and enum symbols is defined within their scope (the
record/enum that defines them). It is an error to define multiple fields or
enum symbols with the same name in a single type. Fields and enum symbols
across scopes are never equal, so field names and enum symbols can be reused in
a different type.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
