Update runtime files.
diff --git a/runtime/doc/todo.txt b/runtime/doc/todo.txt
index 454c0c2..2e65918 100644
--- a/runtime/doc/todo.txt
+++ b/runtime/doc/todo.txt
@@ -1,4 +1,4 @@
-*todo.txt* For Vim version 8.2. Last change: 2020 Nov 28
+*todo.txt* For Vim version 8.2. Last change: 2020 Dec 10
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -38,34 +38,16 @@
*known-bugs*
-------------------- Known bugs and current work -----------------------
-Vim9 - Change
-- Drop support for #{} early December. Close #7310
- -> Does it work to recognize lambda?
- {x: int -> x + 5}
- var int = 5
- {x: int, y: int}
-Vim9 - Making everything work:
-- Compile: for [key, value] in items(map): Also support @r, $VAR, etc.
-- Make map() give an error if the resulting type of the first argument is
- wrong. Only works if the type is known? Is this slow (need to go over all
- items)?
-- Run the same tests in :def and Vim9 script, like in Test_expr7_not()
-- need to check type when a declaration specifies a type: #6507
- let nr: number = 'asdf'
-- Check many more builtin function arguments at compile time.
-- Make sure that in vim9script a function call without namespace only finds
- the script-local function, not a global one.
-- Make sure that where a callback is expected a function can be used (without
- quotes). E.g. sort() and map(). Also at the script level.
-- ":put" with ISN_PUT does not handle range correctly, e.g. ":$-2put".
- Add command to parse range at runtime?
-- When defining an :autocmd or :command, how to specify using Vim9 syntax?
- - always do this when defined in a Vim9 script
- - add some command modifier.
-- For an :autocmd and :command argument, if a following line starts with "|"
- append it. It's like line continuation. (#6702)
+Vim9 - Make everything work:
+- For an :autocmd and :command argument defined in Vim9 script, if a following
+ line starts with "|" append it. It's like line continuation. (#6702)
+- The syntax of a range list[a:b] is ambiguous, is this one "a:b" variable or
+ a range from "a" to "b"? To avoid confusion, require white space before
+ (and after) the colon? #7409
- Implement "export {one, two three}".
- ISN_CHECKTYPE could use check_argtype()
+- Using a script variable inside a :def function doesn't work if the variable
+ is inside a block, see Test_nested_function(). Should it work?
- give error for variable name:
let p = function('NoSuchFunc')
- If a :def function is called with a function reference, compile it to get
@@ -78,7 +60,14 @@
- Does this work already: can use func as reference:
def SomeFunc() ...
map(list, SomeFunc)
+- For builtin functions using tv_get_string*() use check_for_string() to be
+ more strict about the argument type.
- Support passing v:none to use the default argument value. (#6504)
+- Make map() give an error if the resulting type of the first argument is
+ wrong. Only works if the type is known? Is this slow (need to go over all
+ items)?
+- Run the same tests in :def and Vim9 script, like in Test_expr7_not()
+- Check many more builtin function arguments at compile time.
- make 0 == 'string' fail on the script level, like inside :def.
- Check that when using a user function name without prefix, it does not find
a global function. Prefixing g: is required.
@@ -107,9 +96,11 @@
- expandcmd() with `=expr` in filename uses legacy expression.
- eval_expr() in ex_cexpr()
- eval_expr() call in dbg_parsearg() and debuggy_find()
-New syntax and functionality:
Improve error checking:
- "echo Func()" is an error if Func() does not return anything.
+Before launch:
+- Add all the error numbers in a good place in documentation.
+- In the generic eval docs, point out the Vim9 syntax where it differs.
Also:
- For range: make table of first ASCII character with flag to quickly check if
it can be a Vim9 command. E.g. "+" can, but "." can't.
@@ -184,6 +175,8 @@
- "cc" does not call inserted_bytes(). (Axel Forsman, #5763)
- Combining text property with 'cursorline' does not always work (Billie
Cleek, #5533)
+- Should we let the textprop highlight overrule other (e.g. diff) highlight if
+ the priority is above a certain value? (#7392)
- See remarks at top of src/textprop.c
'incsearch' with :s: