-
Notifications
You must be signed in to change notification settings - Fork 0
/
error_explanations.yaml
105 lines (80 loc) · 3.44 KB
/
error_explanations.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
lexing:
Unexpected_character: >
This error is raised when the compiler's input contains
an unexpected character, such as non-ascii characters.
Illegal_escape: >
This error is raised when a string or character literal
contains an invalid escape sequence. Valid escape sequences
include the following: \a, \b, \f, \n, \r, \t, \v, \\, \', \", \0.
Unterminated_string: >
This error is raised when a string isn't terminated by a ".
Invalid_literal: >
This error is raised when an integer, float or character
literal contains invalid digits or an invalid character.
syntax:
Expected: >
This error is raised when a specific token was expected, but
a different token was encountered. For example: the keyword
"in" was expected, but the identifier "im" was found.
Unexpected: >
This error is raised when an unexpected token is encountered.
This means that there is an invalid keyword or symbol.
Unclosed: >
This error is raised when a bracket, parenthesis or brace has not
been closed. For example, when there's a "(", but no closing ")".
Other: >
This error indicates a miscellaneous syntax error.
type:
Expected: >
This error is raised when a specific type was expected but
another type was found. This means that a value or function
is of the wrong type.
Expected_function: >
This error is raised when a function type was expected, but
another non-function type was found. This error occurs when,
for example, it is attempted to call a non-function value.
Recursive_type: >
This error indicates a recursive type, which is not supported.
Use_of_unbound: >
This error is raised when a undefined type or variable is used.
Often this is caused by a simple typo.
Use_of_invalid_primitive: >
This error is raised when it is attempted to use an invalid
primitive operator, such as "#wrong".
Has_no_symbol: >
This error is raised when trying to import- or use a symbol
that does not exist from a module or file.
Cannot_private: >
This error is raised when it is attempted to import- or use
a private symbol from a module. Note that symbols starting
with an underscore are implicitly private to their module.
Cannot_import_from: >
This error is raised when it is attempted to import a symbol
from a value/symbol that isn't a module.
Could_not_infer: >
This error indicates that the type of a value could not be
inferred. Usually this can be solved with type annotations.
Other: >
This error indicates a miscellaneous type error.
other:
Could_not_open: >
This error is raised when a file could not be opened. Usually
this is because the file in question does not exist.
Cannot_import_dir: >
This error is raised when it is attempted to import a directory.
This is not supported.
Could_not_compile: >
This error is raised when compilation of a file failed due to
previous errors.
Failed_to_import: >
This error is raised when importing a file failed due to errors
originating from that file.
Cannot_explain: >
This error is raised when an invalid error code is passed with
the `--explain` command-line option.
Nonexistent_pass: >
This error is raised when a nonexistent pass is passed with
the `--pass` or `-p` command-line option.
Invalid_opt_level: >
This error is raised when an invalid optimization level is passed
with the `-O` command-line option.