-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to latest solc 0.5.8 #616
Conversation
c7f7fa2
to
f7e531e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you consider an UnlockedToken.sol
that inherits our Token and unlocks itself in the constructor? Would save the .unlock()
everywhere, but probably too clever for our own good.
truffle.js
Outdated
@@ -34,7 +34,7 @@ module.exports = { | |||
} | |||
}, | |||
mocha: { | |||
reporter: "mocha-circleci-reporter", | |||
reporter: "eth-gas-reporter", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mistakenly commited?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes :(
Not a bad idea with the |
No, was just wondering. It'd have pros and cons, so happy to leave as-is. |
as these have an issue with the latest solc 0.5.8 Logged dapphub/ds-note#4
…nstances of our own Token
d0fcea4
to
0fa0a71
Compare
Also due to dapphub/ds-note#4 removed
DSToken
from tests and instead use instances of our ownToken