./some_dir/[foo] worked because the AST resulted in an infix node
for the second directory separator / , but a prefix node when
using ./[foo] , importEval now takes this into account. A test
has been included along with the fix.
Along with this change some preexisting import statement tests were
adjusted away from using when false to flag known issues to the
builtin testament functionality of the knownissue field.
Summary
Attempts to import modules using relative import with multiple module syntax like
import ./[foo, bar]
no longer result in an error.Fixes: https://github.com/nim-works/nimskull/issues/1430
Details
./some_dir/[foo]
worked because the AST resulted in aninfix
node for the second directory separator/
, but aprefix
node when using./[foo]
,importEval
now takes this into account. A test has been included along with the fix.Along with this change some preexisting import statement tests were adjusted away from using
when false
to flag known issues to the builtin testament functionality of theknownissue
field.