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

feat: parse range constraints from binfile #375

Merged
merged 4 commits into from
Nov 5, 2024

Commits on Nov 4, 2024

  1. Initial outline

    This puts in place code for detecting range constraints.
    DavePearce committed Nov 4, 2024
    Configuration menu
    Copy the full SHA
    32e4ef3 View commit details
    Browse the repository at this point in the history

Commits on Nov 5, 2024

  1. Initial implementation of range constraints

    This puts through an initial (and rather rough) implementation of range
    constraints.  Its a big confusing at this stage, since we currently have
    a notion of "TypeConstraint" and "RangeConstraint".
    DavePearce committed Nov 5, 2024
    Configuration menu
    Copy the full SHA
    72d3954 View commit details
    Browse the repository at this point in the history
  2. Remake type constraint as a range constraint

    This simply refactors the existing TypeConstraint to use a bound rather
    than a type.  This is a precursor to replacing the existing
    RangeConstraint with this.
    DavePearce committed Nov 5, 2024
    Configuration menu
    Copy the full SHA
    b09be07 View commit details
    Browse the repository at this point in the history
  3. Replace RangeConstraint with TypeConstraint

    This completely eliminates the old RangeConstraint and replaces it with
    the modified TypeConstraint.
    DavePearce committed Nov 5, 2024
    Configuration menu
    Copy the full SHA
    fd72633 View commit details
    Browse the repository at this point in the history