vim9jit

Ok, hear me out. vim9script... but in lua... so fast

What??

So, here's my plan that I'm messing around with:

Write a vim9script parser using Lua(jit) & LPEG
Write a generator from vim9script AST-like nodes -> Lua code.
Write wrappers to make it so that when a file sees vim9script, what it does instead is generate and expose the code in the correct way.
???
Profit.

Why?

Well if we can just make languages whenever we want, why not make parsers and generators whenever we want :)

Also, fun.

Notes:

It is unlikely that we will implement the type checking features from Vim 9 (although that could be fun :laugh:). However, to get your code type checked, you probably can just run it in Vim 9. This is more about a compatibility layer than it is about re-implementing everything.

For example, at the moment, I plan for const and final to simply be variables. I do not plan on creating the ability to error when editing these items.

Status

Can parse
- vim9script vs. old
  - Need to be able to parse an old vim file, and then just the vim9 def as well?...
- Expressions
  - With type definitions
  - Simple arithmetic expressions
  - Strings
    - concatentation
    - indexing (character index)
  - Multiplication
  - List definitions
  - Numbers
    - Decimal numbers
    - Floats
    - Hex
    - Literal blobs
  - Dictionary definitions
    - Old style dicts
    - Literal dicts
    - Literal dicts with no #
  - Vim-isms
    - Global variables
    - Buffer variables
    - Tab variables
    - Window variables
    - Script-local variables
      - Referencing them later
  - Conditionals
  - If statements
    - Simple if statements
    - Else statements
    - Elseif statements
    - Exact vim semantics for if statements
      - Lots of new semantics for boolean conditions
  - Function calls
    - Local functions (implemented in pure lua)
    - Builtin functions (called using vim.fn)
    - Script local functions (exposed)
  - Commands
- Comments
  - Simple comments
  - Need to also handle translation of old vim stuff w/ the # command?
- Func defitions
  - Function argument typing
  - Function return typing
  - Optional arguments
  - Arguments with defaults
  - Exporting
  - Spread def MyFunc(...itemlist: list<number>)
  - Legacy function definitions
    - Legacy function definitions intersperesed.
  - Lambdas
    - { k, v -> asdf }
    - (arg) => expr
- For loops
  - Simple loops
  - Optimized range
- Importing functions
- Auto sourcing / finding functions
- vim9script noclear
- block syntax :help :var
- Manage starting with a colon / handling Ex expressions?
- Lost of new whitespace stuff

Performance?

Well, it would be pretty funny if luajit outperformed native vim9script. We'll have to see.

UPDATE:

vim9script

let start = reltime()

def VimNew(): number
  let sum = 0
  for i in range(1, 2999999)
    sum = sum + i
  endfor

  return sum
enddef

echo VimNew()
echo reltimestr(reltime(start))

" Result:
" 4499998500000
" 0.082964

--[=[
Original vimscript
vim9script

let start = reltime()

def VimNew(): number
  let sum = 0
  for i in range(1, 2999999)
    sum = sum + i
  endfor

  return sum
enddef

echo VimNew()
echo reltimestr(reltime(start))

--]=]

local start = vim.fn['reltime']()
local function VimNew()
  local sum = 0
  for i = 1, 2999999, 1 do
    sum = sum + i
  end
  return sum
end
vim.cmd(string.format([[%s %s]], 'echo', VimNew()))
vim.cmd(string.format([[%s %s]], 'echo', vim.fn['reltimestr'](vim.fn['reltime'](start))))

--4499998500000
-- 0.002857

So... looks like we're pretty fast ;)

Non-Goals

I don't think I want to write all the code that actually does the type checking and what not that is now going to be included in vim9script. I think I'll just pass that off to testing your code in vim9 (at least for now).

I will at least attempt to parse and keep that information for use later if desired.

Examples

You can see the results in ./vim9_scripts/ where there are *.vim files and corresponding *.lua files that I've generated. I'll be adding more examples there later.

numToStr/vim9jit