neovim/runtime/lua/vim/version.lua, branch masterVim-fork focused on extensibility and usabilityhttp://git.waynecole.info/neovim/atom?h=master2026-04-08T17:33:00Zfeat(vim.version): add __eq to vim.VersionRange #388812026-04-08T17:33:00Zngicks94618820+ngicks@users.noreply.github.com2026-04-08T17:33:00Zurn:sha1:a165eee64fa628045241b200d150b0f1e7737301
Problem: vim.VersionRange had no __eq metamethod, so comparing 2 distinct
but same value instances always returned false. In vim.pack.add this caused
redundant lockfile rewrites, even when the resulting lockfile content was
unchanged.
Solution: Add __eq metamethod on vim.VersionRangerefactor: rename _ensure_integer => _assert_integer2026-03-13T19:32:01ZJustin M. Keyesjustinkz@gmail.com2026-03-12T16:10:00Zurn:sha1:017d8aa298254f887a2df1983039f3d678d3ed1arefactor: integer functions, optimize asserts #341122026-03-12T15:04:05ZLewis Russelllewis6991@gmail.com2026-03-12T15:04:05Zurn:sha1:ce1154048b11cdc402d0e5da352a3adca19afb56
refactor(lua): add integer coercion helpers
Add vim._tointeger() and vim._ensure_integer(), including optional base
support, and switch integer-only tonumber()/assert call sites in the Lua
runtime to use them.
This also cleans up related integer parsing in LSP, health, loader, URI,
tohtml, and Treesitter code.
supported by AIrefactor(lua): use vim.system #347072025-07-24T03:03:30ZYochem van Rosmalengit@yochem.nl2025-07-24T03:03:30Zurn:sha1:35af766de6ee2436a4b24495fb862383d16b419dMerge #34715 vim.version improvements2025-07-01T11:19:42ZJustin M. Keyesjustinkz@gmail.com2025-07-01T11:19:42Zurn:sha1:f731766474901e5e345e0ca630315ef69122e556feat(vim.version): add `vim.version.intersect()`2025-06-30T17:59:44ZEvgeni Chasnovskievgeni.chasnovski@gmail.com2025-06-30T13:08:39Zurn:sha1:773075b2bce8f2193343c0efa73f02b1f370dc67
Problem: No way to compute intersection of two version ranges, which is
useful when computing version range that fits inside several reference
ranges.
Solution: Add `vim.version.intersect()`.
fix(vim.version): improve construction of '<=a.b.c' and '>a.b.c' ranges2025-06-30T17:59:12ZEvgeni Chasnovskievgeni.chasnovski@gmail.com2025-06-30T13:08:37Zurn:sha1:649ff924d990003e9d9338d964a206e7c7a5c144
Problem: `vim.version.range('<=a.b.c')` is not precise when it comes to
its right hand side. This is due to version ranges using exclusive right
hand side. While `vim.version.range('>a.b.c')` is not precise when it
comes to its left hand side because left hand sides are inclusive.
Solution: For '>=a.b.c' increase `to` from 'a.b.c' to the smallest
reasonable version that is bigger than 'a.b.c'. For '<a.b.c' do the same
for `from`.
More proper solution is an explicit control over inclusivity of version
range sides, but it has more side effects and requires design decisions.
doc(vim.version): options formatting #347162025-06-30T16:55:29ZJames Trew66286082+jamestrew@users.noreply.github.com2025-06-30T16:55:29Zurn:sha1:4034476dd362b577024cfe6cac011ed82ef1ef38feat(vim.version): make `tostring()` return human-readable version range2025-06-30T13:08:56ZEvgeni Chasnovskievgeni.chasnovski@gmail.com2025-06-30T13:08:35Zurn:sha1:aeb8bca12ddfe741569df622ef0cbc90211a6064
Problem: `tostring()` applied to version range doesn't return
human-readable text with information about the range.
Solution: Add `__tostring()` method.
docs(vim.version): document `vim.VersionRange` as a dedicated class2025-06-30T13:08:30ZEvgeni Chasnovskievgeni.chasnovski@gmail.com2025-06-30T13:08:30Zurn:sha1:561021bacd8e9f4acc01efe99b03c70e5dd8accb