Thanks very much. > > * if Vim9 script remains experimental, presumably I have to explicitly > > enable it within a script it somehow/somewhere? Or is this the > > vim9script reference above? > > The Vim9 script syntax is only used for functions defined with ":def" > and for scripts that start with "vim9script".
I seem to recall from the other threads on Vim9 that the reason for using :def is that the changes for Vim9 script will not be backwards compatible. What about the other way around? Is there a mode in which we can run Vim such that :function declared functions run as if declared via :def? And similarly for scripts, running in this mode would obviate the need for "vim9script"? If not, do you have a script rewriter planned, to help people with the migration? Apologies if I missed these points from the other Vim9 threads. <snip> > > * I'm assuming that channel support will remain the same? Is there any > > speed improvements we can investigate here? > > Nothing changes for channel support. Except that when you use a ":def" > function to build a request or unpack a response that should be a lot > faster. Thanks. The rationale behind this question and the questions above is me trying to work out how best we experiment with these changes with govim. I, and I'm sure many other people, would like to avoid having to rewrite existing VimScript where possible, especially whilst things are experimental. But at the same time it would seem to make sense to exercise the proposed changes as much as possible as early as possible. Best, Paul -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CACoUkn45W%3D8kNUUPfv1VPZXia3MZuec1DcxP0-f4zQ16SOV3hw%40mail.gmail.com.
