| commit | 447ada82a1432be07212a901e9ebfd112ac1317e | |
| author | Paul Vick <paulvick@fb.com> | |
| Fri, 22 Jul 2022 19:03:52 +0000 (22 12:03 -0700) | ||
| committer | Facebook GitHub Bot <facebook-github-bot@users.noreply.github.com> | |
| Fri, 22 Jul 2022 19:03:52 +0000 (22 12:03 -0700) | ||
| tree | f6cd89cc6cfa733f9a43a00fbaa67cb68c7a99b5 | treesnapshot (tar.gz zip) |
| parent | 4f23fe767571e71d40a9eac3b819e8734ffa8a03 | commitdiff |
Allow nested module names
Summary:
As a part of the module references work, modules now are allowed to be nested inside one another. So module `x.y.z` is module `z` nested inside module `y` which is nested inside module `x`.
At the moment, there is no practical semantics assigned to nested modules, they're really just a module name with dots in them. So the parser parses them as qualified names, but once they are translated into the type checker, they just become regular names (that happen to have dots in them).
Reviewed By: oulgen
Differential Revision: D37775964
fbshipit-source-id: ea8406bcb3a7ad3444ff3dbd5ef5bced678c282f
Summary:
As a part of the module references work, modules now are allowed to be nested inside one another. So module `x.y.z` is module `z` nested inside module `y` which is nested inside module `x`.
At the moment, there is no practical semantics assigned to nested modules, they're really just a module name with dots in them. So the parser parses them as qualified names, but once they are translated into the type checker, they just become regular names (that happen to have dots in them).
Reviewed By: oulgen
Differential Revision: D37775964
fbshipit-source-id: ea8406bcb3a7ad3444ff3dbd5ef5bced678c282f
56 files changed: