diff options
| author | kaizhangNV <149626564+kaizhangNV@users.noreply.github.com> | 2024-12-19 00:27:30 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-18 22:27:30 -0800 |
| commit | f675c39340ac751fcabc1f30604c8ea737fbe57f (patch) | |
| tree | e745cdd3b6682b610098a9722cc562f4fe484506 /tests/expected-example-failure-github.txt | |
| parent | a80575608e0296e1779c2085b893145893e4cc20 (diff) | |
Fix the parser issue for not recognize Generic<T>[N] (#5912)
Close #5911.
In this issue, if we define the generic in source file 1,
and import it into source file 2, then when parsing the
reference of that generic in source file 2, we will not parse
the generic directly, instead we have a logic to speculate it
as generics first with a fake diagnostic sink, and if there is
no error report, we will consider it as a actual generic and will
parse it again.
In this logic, we will also disambiguate the expression based on
the following token, but we didn't consider the token '[', so we
will finally not treat the expression as generic.
The fix is just simply add '[' here.
Co-authored-by: Yong He <yonghe@outlook.com>
Diffstat (limited to 'tests/expected-example-failure-github.txt')
0 files changed, 0 insertions, 0 deletions