You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
Attempts to import modules using relative import with multiple module
syntax like `import ./[foo, bar]` no longer result in an error.
Fixes: #1430
## Details
`./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.
---------
Co-authored-by: zerbina <100542850+zerbina@users.noreply.github.com>
Example
there are a
foo.nim
and abar.nim
in the parent folder of current moduleActual Output
Expected Output
modules are imported properly
Possible Solution
importing one by one each line compiles
if modules are inside a folder from relative parent folder it compiles
References
works on nim
The text was updated successfully, but these errors were encountered: