Building a nonexistent module with a slash in the name triggers build of the selected module

[odisseus]

$ fury -m foobar
The module has not been specified.

$ fury -m foo-bar
The module has not been specified.

$ fury -m foo/bar --output linear
Starting compilation of module fury/io
Successfully compiled module fury/io
...
Starting compilation of module fury/frontend
Successfully compiled module fury/frontend
Starting compilation of module fury/project
Successfully compiled module fury/project

$ fury -m / --output linear
Starting compilation of module fury/io
Successfully compiled module fury/io
...
Starting compilation of module fury/frontend
Successfully compiled module fury/frontend

[szymon-rd]

The same issue appears for building projects. Will try to fix it as well.

[szymon-rd]

Actually, PR was closed not merged, reopening issue due to my mistake.

[odisseus]

The error message does not appear if the wrong module name contains a slash, like foo/bar.

[odisseus]

This issue returned after PR #1223 was merged. Every kind of problem with the module name argument is now treated as if that argument were missing, and the default module is substituted.

[odisseus]

PR #1282 has brought this issue back again. I see a pattern here...