Same name different frames

🟢 Beginner · Lesson 22

binding_name is a SUB-key - the same name under two different frames is two different addresses. (frame, name) is always the full address; names never collide across frames.

Before you run

Use the Beginner guide for prerequisite concepts. Run from a checkout with Melder installed and Python 3.14 free-threading selected. The collection download includes the level's local helper modules.

Run the saved script

python UX_and_AIX_experiences/01_beginner/22_same_name_different_frames.py

py -3.14t UX_and_AIX_experiences/01_beginner/22_same_name_different_frames.py

Download this collection · Source on GitHub

Public surface

the (frame, name) address space

Code

"""
TIER: beginner (22)
GOAL: binding_name is a SUB-key - the same name under two different
      frames is two different addresses. (frame, name) is always the
      full address; names never collide across frames.
SURFACE EXERCISED: the (frame, name) address space
"""
import melder as md


class UsersRepo:
    kind = "repo"


class UsersApi:
    kind = "api"


def main() -> None:
    book = md.Spellbook()
    book.bind(spell=UsersRepo, existence="unique",
              spellframe="storage", binding_name="users")
    book.bind(spell=UsersApi, existence="unique",
              spellframe="web", binding_name="users")
    conduit = book.conjure()

    repo = conduit.meld(spellframe="storage", binding_name="users")
    api = conduit.meld(spellframe="web", binding_name="users")
    assert repo.kind == "repo" and api.kind == "api"
    print("same name, two frames, two addresses: no collision")


if __name__ == "__main__":
    main()

Check the outcome

The script contains its own assertions or demonstrated refusal paths. Run it to evaluate those checks against your installed version. The code above is taken directly from the saved file; no run output is invented here.

More beginner examples · Level guide