> Hmm, it's possible if you ignore security fixes, these sometimes skip a > longer range of patches. > > We could add v:longversion or v:versionlong, with: > > major version (one digit) > minor version (two digits) > patchlevel (four digits) > > Current version would be 8011523. Then you can easily compare with the > version you need, no string parsing or anything.
I'd prefer the semver string to be honest, v8.1.1512. Neovim's releases are also semver tagged. It's also the string the user will know: https://github.com/vim/vim/releases https://github.com/neovim/neovim/tags It's also the string I will output to users saying "hey, you need to be on version X for this feature" Because Go modules is entirely based around semver versions, dealing with them is trivial: https://godoc.org/github.com/rogpeppe/go-internal/module (there is also a more standard package proposed). So, on that front I'm sorted. -- -- 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/CACoUkn4hfy%3D%2BGkR6rB-o3eo4WxvnifNAdncNx0MqBPWG8HXEbw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
