Skip to content
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

Merged
merged 4 commits into from
May 20, 2019
Merged

Upgrade to latest solc 0.5.8 #616

merged 4 commits into from
May 20, 2019

Conversation

elenadimitrova
Copy link
Contributor

@elenadimitrova elenadimitrova commented May 19, 2019

Also due to dapphub/ds-note#4 removed DSToken from tests and instead use instances of our own Token

@elenadimitrova elenadimitrova added this to the Sprint 26 milestone May 19, 2019
@elenadimitrova elenadimitrova self-assigned this May 19, 2019
@elenadimitrova elenadimitrova force-pushed the maintenance/upgrade-solc-0.5.8 branch 3 times, most recently from c7f7fa2 to f7e531e Compare May 19, 2019 13:46
Copy link
Member

@area area left a 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",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mistakenly commited?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes :(

@elenadimitrova
Copy link
Contributor Author

Not a bad idea with the UnlockedToken although I would rather be explicit with the Token model we have unless you mind terribly?

@area
Copy link
Member

area commented May 20, 2019

No, was just wondering. It'd have pros and cons, so happy to leave as-is.

@elenadimitrova elenadimitrova force-pushed the maintenance/upgrade-solc-0.5.8 branch from d0fcea4 to 0fa0a71 Compare May 20, 2019 12:33
@area area merged commit b413f0b into develop May 20, 2019
@area area deleted the maintenance/upgrade-solc-0.5.8 branch May 20, 2019 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants