| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Vim9: imported uninitialized list does not get type checked.
Solution: Get type from imported variable.
|
|
Problem: Vim9: uninitialzed list does not get type checked.
Solution: Set the type when initializing the variable. (closes #8529)
|
|
Problem: Vim9: can use reserved words at the script level.
Solution: Check variable names for reserved words. (closes #8253)
|
|
Problem: Vim9: using "++nr" as a command might not work.
Solution: Do not recognize "++" and "--" in a following line as addition or
subtraction.
|
|
Problem: Vim9: for loop infers type of loop variable.
Solution: Do not get the member type. (closes #8102)
|
|
Problem: Vim9: problem defining a script variable from legacy function.
Solution: Check if the script is Vim9, not the current syntax.
(closes #8032)
|
|
Problem: Vim9: Using #{ for a dictionary gives strange errors.
Solution: Give an error when using #{ for a comment after a command.
|
|
Problem: Vim9: "import * as" does not work at script level.
Solution: Implement using an imported namespace.
|
|
Problem: Not always clear where an error is reported.
Solution: Add the where_T structure and pass it around. (closes #7796)
|
|
Problem: Vim9: wrong error when modifying dict declared with :final.
Solution: Do not check for writable variable when an index follows.
(closes #7657)
|
|
Problem: Vim9: extend() can violate the type of a variable.
Solution: Add the type to the dictionary or list and check items against it.
(closes #7593)
|
|
Problem: Vim9: concatenating lines with backslash is inconvenient.
Solution: Support concatenating lines starting with '|', useful for
:autocmd, :command, etc. (closes #6702)
|
|
Problem: Vim9: error when using :import in legacy script twice.
Solution: Make it possible to redefine an import when reloading.
|
|
Problem: Vim9: crash if script reloaded with different variable type.
Solution: Check the type when accessing the variable.
|
|
Problem: Vim9: no need to keep all script variables.
Solution: Only keep script variables when a function was defined that could
use them. Fix freeing static string on exit.
|
|
Problem: Vim9: variables declared in a local block are not found in
when a function is compiled.
Solution: Look for script variables in sn_all_vars.
|
|
Problem: Vim9: function defined in a block can't use variables defined in
that block.
Solution: First step: Make a second hashtab that holds all script variables,
also block-local ones, with more information.
|
|
Problem: Vim9: can assign wrong type to script dict. (Christian J. Robinson)
Solution: Check the type if known.
|
|
Problem: Vim9: accidentally using "x" causes Vim to exit.
Solution: Disallow using ":x" or "xit" in Vim9 script. (closes #6399)
|
|
Problem: Vim9: no line break allowed in :import command.
Solution: Skip over line breaks.
|
|
Problem: Vim9: some code not tested.
Solution: Add a few more test cases. Reorder checks for clearer error.
Remove unreachable code.
|
|
Problem: Vim9: type is not checked when assigning to a script variable.
Solution: Check the type.
|
|
Problem: Vim9 script variable declarations need a type.
Solution: Make "let var: type" declare a script-local variable.
|
|
Problem: Vim9: import that redefines local variable does not fail.
Solution: Check for already defined symbols.
|
|
Problem: Vim9: insufficient script tests.
Solution: Add more tests. Make "import * as Name" work.
|
|
Problem: Maintaining a Vim9 branch separately is more work.
Solution: Merge the Vim9 script changes.
|
