Could it be possible to have a warning message when installing a rock that contains a module that is already provided by another rock? Or is there already an option for this and I didn't find it?

At least with Luarocks version 3.2.1 I verified that there are no warnings for this case.

However it seems that Luarocks is aware of the collision and installs the new module under another name and

Documentation says:

fun.remove_if(predicate, gen, param, state)
iterator:remove_if(predicate)

An alias for filter().

The name remove_if strongly suggests that elements satisfying the predicate will be removed, keeping only those that do not satisfy the predicate; while filter actually keeps the elements satisfying the predicate.

In other words, the linguistic expec

In the documentation at https://luaposix.github.io/luaposix/modules/posix.poll.html#rpoll the text of the link has the correct url, but the link target is just the page itself. I guess you need to put it in twice at
https://github.com/luaposix/luaposix/blob/master/ext/posix/poll.c#L246

The example shows how to run test cases, but it is difficult to spot among the other pieces of the example, and the output screenshot still shows them running.

Instead of showing how to run a limited set of tests around the middle of the example, perhaps all tests demonstrated in the output could be run at the end.

https://travis-ci.org/tilkinsc/LuaConsole/jobs/491369318

It seems the Mac version clang linker doesn't have the -E command. Rightfully so, it tries to build as linux. We are also missing objcopy.

Create command uses tarantool built-in fio.mktree(), which is not accesible via tarantool version < 1.9 (tested with 1.6, 1.7.6, 1.7-centos and 1.8.1)

Actually fio.mktree() is specified in docs on 1.7 (http://www.tarantool.io:8090/ru/doc/1.7/reference/reference_lua/fio/#fio-mktree)
But I am still unable to call it (using official docker image 1.7.6):

/opt/tarantool # taranto

If the reference option is not set, all template parameters will be cloned recursively. This will result in an infinite loop if there is a reference cycle in the parameters.

This issue doesn't have the highest priority, but I should document that it exists and that I'm aware of it.

• Maybe I should introduce a caveats section in the README.