MemoryAccess.setAddress should take Addressable, not MemoryAddress

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P3
    • None
    • Affects Version/s: repo-panama
    • Component/s: tools

      The API design of "Be liberal in what you accept, and conservative in what you send" seems to suggest that, when setting an address value on a segment, we should be more flexible, and accept an Addressable. Conversely, for getters, it is fine to return MemoryAddress.

            Assignee:
            Maurizio Cimadamore
            Reporter:
            Maurizio Cimadamore
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: