@@ -1033,10 +1033,12 @@ In Vim9 script one can use the following predefined values: >
1033
1033
null
1034
1034
null_blob
1035
1035
null_channel
1036
+ null_class
1036
1037
null_dict
1037
1038
null_function
1038
1039
null_job
1039
1040
null_list
1041
+ null_object
1040
1042
null_partial
1041
1043
null_string
1042
1044
`true` is the same as `v: true ` , `false` the same as `v: false ` , `null` the same
@@ -1555,7 +1557,7 @@ string to a number.
1555
1557
1556
1558
If a type is given where it is not expected you can get *E1272* .
1557
1559
1558
- If a type is incomplete you get *E1363*, e.g. when you have an object for
1560
+ If a type is incomplete you get *E1363* , e.g. when you have an object for
1559
1561
which the class is not known (usually that is a null object).
1560
1562
1561
1563
Type inference ~
@@ -1754,7 +1756,7 @@ Exporting an item can be written as: >
1754
1756
export interface MyClass ...
1755
1757
< *E1043* *E1044*
1756
1758
As this suggests, only constants, variables, `:def ` functions and classes can
1757
- be exported. {not implemented yet: class, interface}
1759
+ be exported.
1758
1760
1759
1761
*E1042*
1760
1762
`:export ` can only be used in Vim9 script, at the script level.
@@ -1787,7 +1789,7 @@ filename. For example: >
1787
1789
Then you can use "that.item", etc. You are free to choose the name "that".
1788
1790
Use something that will be recognized as referring to the imported script.
1789
1791
Avoid command names, command modifiers and builtin function names, because the
1790
- name will shadow them. Better not start the name starts with a capital
1792
+ name will shadow them. It's better not to start the name with a capital
1791
1793
letter, since it can then also shadow global user commands and functions.
1792
1794
Also, you cannot use the name for something else in the script, such as a
1793
1795
function or variable name.
@@ -1860,9 +1862,9 @@ However, the namespace cannot be resolved on its own: >
1860
1862
<
1861
1863
This also affects the use of | <SID> | in the legacy mapping context. Since
1862
1864
| <SID> | is only a valid prefix for a function and NOT for a namespace, you
1863
- cannot use it
1864
- to scope a function in a script local namespace. Instead of prefixing the
1865
- function with | <SID> | you should use | <ScriptCmd> | . For example: >
1865
+ cannot use it to scope a function in a script local namespace. Instead of
1866
+ prefixing the function with | <SID> | you should use | <ScriptCmd> | . For example:
1867
+ >
1866
1868
noremap ,a <ScriptCmd>:call s:that.OtherFunc()<CR>
1867
1869
<
1868
1870
*:import-cycle*
0 commit comments