Update

Author: mattqual

TODO

@@ -11,7 +11,7 @@
 - [70%] Variables
 - [70%] Virtual variables
 - [70%] Methods
-- [ ] Aliases
+- [x] Aliases
 - [ ] Generics
 - [ ] Lexical scopes
 - [ ] Default lexical scope

src/SUMMARY.md

@@ -34,4 +34,5 @@
 - [Interfaces](./interfaces.md)
 - [Variables](./variables.md)
 - [Virtual variables](./virtual-variables.md)
-- [Methods](./methods.md)
+- [Methods](./methods.md)
+- [Aliases](./aliases.md)

src/aliases.md

@@ -0,0 +1,20 @@
+# Aliases
+
+Aliases are used in different places of the language:
+
+```
+import CT = com.business.coreRT.enum.ContactType;
+type U = (decimal, String);
+namespace special_version;
+```
+
+## Documentation comment
+
+An alias may be prefixed by a documentation comment.
+
+```
+/** Comment */
+type Params = {
+    x : decimal,
+};
+```

src/packages.md

@@ -58,4 +58,32 @@ A `package` definition may have a prefix documentation comment, allowing to docu
  * Enumerations used in the core runtime.
  */
 package com.business.coreRT.enum {}
+```
+
+## Package wildcard import
+
+A package wildcard import is aliased for the following directive:
+
+```
+import q = com.business.quantum.*;
+```
+
+Then `q` may be used as a qualifier to resolve to a name in the `quantum` package (excluding subpackages).
+
+```
+q::x
+```
+
+## Package recursive import
+
+A package recursive import is aliased for the following directive:
+
+```
+import q = com.business.quantum.**;
+```
+
+Then `q` may be used as a qualifier to resolve to a name in the `quantum` package and its subpackages in a recursive way.
+
+```
+q::x
 ```

src/types/structural-object.md

@@ -1,6 +1,6 @@
 # Structural object
 
-Structural object types, `{ ... }`, are simple property records, whose field order and documentation comments are sensitive. Those types are compiled into efficient structures.
+Structural object types, `{ ... }`, are simple property records, whose field order is sensitive. Those types are compiled into efficient structures.
 
 ```
 type N1 = { x : decimal, y : decimal };
@@ -22,13 +22,9 @@ All fields are optional; however, if it is desired to default to `undefined`, a
 
 Due to sensitive field order, structural object types with equivalent fields but in different orders will be incompatible.
 
-## Documentation comments
-
-Due to sensitive documentation comments, structural object types with equivalent fields (including their order) but differing documentation comments in their fields will be incompatible.
-
 ## Compatibility
 
-Two structural object types are compatible only if either a\) one is used as a subset of another or b\) fields are equivalent and consist of the same order and the same documentation comments.
+Two structural object types are compatible only if either a\) one is used as a subset of another or b\) fields are equivalent and appear in the same order.
 
 ## Rest