fixup! Add EEP for native records

Author: bjorng

eeps/eep-0079.md

@@ -297,12 +297,9 @@ from the current native-record definition, namely:
 
 * Whether it is exported (through `-export_record`)
 
-The runtime needs the current native-record definition to perform
-create and update operations.
-
-However, to perform read operations on native-record values — accessing
-native-record fields and pattern matching over native-record values —
-the runtime does not consult the current native-record definition.
+The runtime needs the current native-record definition to create a
+record. It does not use native-record definition when updating or
+reading values from a record.
 
 To minimize the ambiguity of the next sections we would use more verbose wording:
 
@@ -327,15 +324,18 @@ Expr#Module:Name.Field
 These expressions return the value of the specified field of the
 native-record value.
 
+When a field from a native-record value is accessed, the native-record
+definition is **not** consulted.
+
 An access operation fails with a `{badrecord,Expr}` error if:
 
-* The native-record value is not visible at the call site (the
-  native record is not exported and is used outside of the defining
-  module).
+* When the native-record value was created, the definition of the
+  record was not exported, and it is now used outside its definining
+  module.
 
 * `Expr` does not evaluate to a native-record value of the expected
-  type `#Name` or `#Module:Name` (that is, it is either not a native record
-  at all or it is some other term).
+  type `#Name` or `#Module:Name` (that is, it is either not a native
+  record at all or it is another native record).
 
 An access operation fails with a `{badfield,Field}` error if:
 
@@ -356,6 +356,10 @@ This access operation fails with a `{badfield,Field}` error if:
 
 * The field `Field` is not defined in the native-record value.
 
+* When the native-record value was created, the definition of the
+  record was not exported, and it is now used outside its definining
+  module.
+
 ### Updating native records
 
 The syntax for updating native-record values:
@@ -367,17 +371,19 @@ Expr#Module:Name{Field1=Expr1, ..., FieldN=ExprN}
 
 Field names must be atoms.
 
-A native-record value is updated according to its native-record definition.
+When a native-record value is updated, its native-record definition is
+**not** consulted.
 
 An update operation fails with a `{badrecord,Expr}` error if:
 
-* The native-record definition is not visible at the call site (the
-  native record is not exported from `Module`).
+* When the native-record value was created, the definition of the
+  record was not exported, and it is now used outside its definining
+  module.
 
 An update operation fails with a `{badfield,FN}` error if:
 
 * The native-record update expression references the field FN which is
-  not defined (in the structure definition).
+  not defined native-record value.
 
 Native-record update expressions are not allowed in guards.
 
@@ -389,6 +395,16 @@ The following syntax allows update any record having the given fields:
 Expr#_{Field1=Expr1, ..., FieldN=ExprN}
 ```
 
+An update operation fails with a `{badrecord,Expr}` error if:
+
+* When the native-record value was created, the definition of the
+  record was not exported, and it is now used outside its definining
+  module.
+
+* `Expr` does not evaluate to a native-record value of the expected
+  type `#Name` or `#Module:Name` (that is, it is either not a native
+  record at all or it is another native record).
+
 An anonymous update operation fails with a `{badfield,FN}` error if:
 
 * The native-record update expression references the field FN which is
@@ -408,11 +424,14 @@ The syntax:
 
 Here, `Expr1`, .. `ExprN` are patterns, and Field names must be atoms.
 
+When a native-record value is matched, its native-record definition is
+**not** consulted.
+
 Pattern matching fails if:
 
-* The native-record value is not visible at the call site, that is,
-  an attempt is made to match out a a value from a non-exported record
-  from a module other than its defining module.
+* When the native-record value was created, the definition of the
+  record was not exported, and it is now used outside its definining
+  module.
 
 * The pattern references a FieldK and the native-record value does not
   contain this field.
@@ -487,6 +506,11 @@ If `Module` is a module name and `Name` is an atom, the predicate
 returns true if term `Term` is a native-record value with the
 corresponding native-record name.
 
+This function will only check that `Term` is a native record with
+`Name` created from the given the module. It will not check whether
+the native record is still defined in the given module, nor whether
+it is exported.
+
 Example:
 
 ```erlang
@@ -517,6 +541,9 @@ an imported native record.
 If `is_record/2` is used in a function body, `Name` is allowed to be a
 variable.
 
+If `Name` refers to an imported native record, see the description of
+`is_record/3` for more details.
+
 Examples:
 
 ```erlang