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
I recently updated to Nim 2.0 but I am experiencing some unexpected behavior since the upgrade
What is the problem?
Prior to 2.0, one could use nim develop to put a symlink to a package I am working on while developing. This worked great; when the package changed the scripts using the modules where automatically changed. On 2.0, however, this behavior does not happen anymore.
Steps to reproduce
Create a package using nimble
mkdir simplePackage && nimble init
nimble develop
Then using a simple scripts invoke the package
# test.nimimport simplePackage
echoadd(1, 1)
which outputs 2.
Now when we edit the add function as follows
#file: src/simplePackage.nimprocadd*(x, y: int): int=## Adds two numbers together.echo"hello!!"return x + y
it still outputs 2, without hello!!. This behavior does not happen in 1.6.x and pertains even after cleaning the binary . A combination of uninstalls and installs works. I believe running a unittest for some reason also includes the changes in one shot. other scripts are left out for some reason.
Hi all,
I recently updated to Nim 2.0 but I am experiencing some unexpected behavior since the upgrade
What is the problem?
Prior to 2.0, one could use
nim develop
to put a symlink to a package I am working on while developing. This worked great; when the package changed the scripts using the modules where automatically changed. On 2.0, however, this behavior does not happen anymore.Steps to reproduce
Create a package using nimble
mkdir simplePackage && nimble init
nimble develop
Then using a simple scripts invoke the package
which outputs 2.
Now when we edit the add function as follows
it still outputs 2, without
hello!!
. This behavior does not happen in 1.6.x and pertains even after cleaning the binary . A combination of uninstalls and installs works. I believe running a unittest for some reason also includes the changes in one shot. other scripts are left out for some reason.This issue is related to (#1124)
The text was updated successfully, but these errors were encountered: