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
Does diffusec still function properly even when the new version deviates from the original? For instance, if the old version is 0.6.* and the new version is 0.7.*, will diffusec continue to work? I am faced with two separate projects in this particular situation, and it seems like diffusc have encountered difficulties finding a compatible version that works for both compilations.
Code example to reproduce the issue:
contract v1 0.6.12 contract v2 0.7.12
Version:
1.0.0
Relevant log output:
No response
The text was updated successfully, but these errors were encountered:
In the generated contract DiffFuzzUpgrades.sol, could you try changing ^0.6.12 to >=0.6.12 and see if that compiles? If so, the fix should be fairly straightforward on my end.
Also, for what it's worth, soon I will be merging a PR which changes the flag for specifying the solc version to use from -v and --version to -V and --solc-version, so that the --version flag behaves the way most people would expect, printing the version of the tool itself. So for your case, when running the tool you would use: diffusc v1_path v2_path --solc-version 0.6.12.
Describe the issue:
Does diffusec still function properly even when the new version deviates from the original? For instance, if the old version is
0.6.*
and the new version is0.7.*
, will diffusec continue to work? I am faced with two separate projects in this particular situation, and it seems likediffusc
have encountered difficulties finding a compatible version that works for both compilations.Code example to reproduce the issue:
contract v1 0.6.12
contract v2 0.7.12
Version:
1.0.0
Relevant log output:
No response
The text was updated successfully, but these errors were encountered: