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

[proposed] Update BytecodeObject validation requirements #124

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Commits on Aug 22, 2018

  1. Clarify formal bytecode object requirements

    - Define separate `UnlinkedBytecodeObject` and `LinkedBytecodeObject`
    - Use those respectively for `ContractType` and `ContractInstance`
    - Ensure unlinked bytecode always requires `link_references`
    - Update examples to specify `[]` for bytecode that doesn't link
    gnidan committed Aug 22, 2018
    Configuration menu
    Copy the full SHA
    6b6eb76 View commit details
    Browse the repository at this point in the history
  2. Remove BytecodeObject, leave only Unlinked/Linked

    Because the inheritance makes some tools not work right
    gnidan committed Aug 22, 2018
    Configuration menu
    Copy the full SHA
    ac6e35c View commit details
    Browse the repository at this point in the history