Commits
- Commit:
51569221d2baa264eb1de2b71122325e6131ccb2
- From:
- Sergey Bronnikov <sergeyb@tarantool.org>
- Date:
luajit: bump new version
* Fix BC_UCLO insertion for returns.
Part of #8825
NO_DOC=LuaJIT submodule bump
NO_TEST=LuaJIT submodule bump
NO_CHANGELOG=LuaJIT submodule bump
- Commit:
0c53d22b583fe233b13bdd161cd744dcbb2774dd
- From:
- Igor Munkin <imun@tarantool.org>
- Via:
- Igor Munkin <imun@cpan.org>
- Date:
exports: clean up LuaJIT public interfaces
There was a little mess in exports file regarding LuaJIT symbols to be
visible from Tarantool binary, so some functions (e.g. <lua_tonumberx>
and <lua_tointegerx>) were hidden unintentionally. As a result of the
patch almost all public LuaJIT symbols are exported from Tarantool
binary; there are still several functions reasonably hidden (you can
find the rationale around the corresponding cases in the test file).
Closes #3680
@TarantoolBot document
Title: clean up LuaJIT exported functions
The list of the LuaJIT-related functions being exported (i.e. public)
from Tarantool should be updated. The actual list of the exported
symbols can be found within changeset (either extra/exports file or
related Lua test chunk).
- Commit:
5f6d367c51f7545a940119e7a393baf982b80f3f
- From:
- Gleb Kashkin <g.kashkin@tarantool.org>
- Via:
- Igor Munkin <imun@cpan.org>
- Date:
compat: add is_new and is_old to options
It used to be somewhat complicated to check the effective value
of a compat option, because `<option_name>.current` could contain
'default' state.
This patch introduces helper functions that take care of that.
The following alternatives were considered:
* `compat.<option_name>.effective` - it is excessive in the presence
if `current` and `default`, and is visible in serialization
* `compat.<option_name>.get()` - while it is a function, it does only
half of the work required, user still has to compare result to 'new'
Closes #8807
@TarantoolBot document
Title: Add `:is_new/old()` helpers to tarantool.compat options
`compat.<option_name>.current` can be 'new', 'old' or 'default',
thus when it is default there must be an additional check if
`compat.<option_name>.default` is 'new'. It is handier to have a
helper to deal with that instead of complicated `if`:
* check if effective value is 'new' before the patch:
```lua
if compat.<option_name>.current == 'new' or
(compat.<option_name>.current == 'default' and
compat.<option_name>.default == 'new') then
...
end
```
* after the patch:
```lua
if compat.<option_name>:is_new() then
...
end
```
Please update [tutorial on using compat], maybe add an example to
[Listing options details].
[tutorial on using compat]: https://www.tarantool.io/en/doc/latest/reference/reference_lua/compat/compat_tutorial/
[Listing options details]: https://www.tarantool.io/en/doc/latest/reference/reference_lua/compat/compat_tutorial/#listing-options-details
- Commit:
294f2d616c12334b0b9344ee21399bea932c3538
- From:
- Mergen Imeev <imeevma@tarantool.org>
- Via:
- Alexander Turenko <totktonada.ru@gmail.com>
- Date:
config: introduce remaining vinyl options
This patch introduces all remaining vinyl options that have not been
introduced before.
Part of #8861
NO_DOC=Was already described before.
- Commit:
10ff3a31bf80a74ae39654ca6ca68ab59905a94d
- From:
- Mergen Imeev <imeevma@tarantool.org>
- Via:
- Alexander Turenko <totktonada.ru@gmail.com>
- Date:
config: fix error message during reload
Prior to this patch, if a cluster configuration was not present or an
instance was not found in the configuration during a reload, the error
would begin with 'Startup failure'. Now it starts with 'Reload failure'
in these cases.
Part of #8862
NO_DOC=fix of error message