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

Changed uint80 to uint #40

Merged
merged 3 commits into from
Sep 5, 2018
Merged

Changed uint80 to uint #40

merged 3 commits into from
Sep 5, 2018

Conversation

ben-kaufman
Copy link
Contributor

@ben-kaufman ben-kaufman commented Sep 5, 2018

Fix: #39
Changed uint80 to uint.
Linter fixes.
ERC165 identifier updated.
Regenerated docs.

Changed uint80 to uint.
Linter fixes.
ERC165 identifier updated.
Regenerated docs.
docs/index.html Outdated
@@ -1,5 +0,0 @@
<!--redirect to /README-->
Copy link
Contributor

Choose a reason for hiding this comment

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

Why was this removed?

docs/README.md Outdated
@@ -1,3 +0,0 @@
# Welcome to DAOstack Access Control Docs
Copy link
Contributor

Choose a reason for hiding this comment

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

Why was this removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't know. I just re-generated the docs...

Copy link
Contributor

Choose a reason for hiding this comment

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

yarn docs:<..> only touches docs/generated_docs

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I might have accidentally deleted them... I added them back.

@tsuberim tsuberim merged commit 0e96a84 into master Sep 5, 2018
@tsuberim tsuberim deleted the return-to-uint256 branch September 5, 2018 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

uint80 is more expansive on read(unlock) and cheaper in write(lock) re uint256
2 participants