Skip to content

codegen should ideally not need to know the optimization level #123958

Closed

Description

@iritkatriel

Optimization level is used for things that can be done in ast_opt. I'll try to move them there.

Linked PRs

Activity

  1. self-assigned this
    on Sep 11, 2024
  2. added a commit that references this issue on Sep 11, 2024
  3. hugovk commented on Sep 15, 2024

    @hugovk
    Member

    PR merged, closing issue.

  4. iritkatriel commented on Sep 15, 2024

    @iritkatriel
    MemberAuthor

    There's another usage still to remove.

  5. hugovk commented on Sep 15, 2024

    @hugovk
    Member

    Thanks, sorry I was too quick with the close button :)

  6. Eclips4 commented on Sep 15, 2024

    @Eclips4
    Member

    So, the only remaining occurrence of OPTIMIZATION_LEVEL is related to the assert statement.
    @iritkatriel, are you currently working on this? If not, can I attempt to fix it?

  7. iritkatriel commented on Sep 15, 2024

    @iritkatriel
    MemberAuthor

    I have a patch for it. Thanks.

  8. added a commit that references this issue on Sep 16, 2024
  9. iritkatriel commented on Sep 17, 2024

    @iritkatriel
    MemberAuthor

    I got as far as I could with this, the assert optimization needs to stay in ast_opt (see discussion on PR).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

interpreter-core(Objects, Python, Grammar, and Parser dirs)

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions