Skip to content

Address variance conformance gaps: variance in base class specializations #2263

Closed

Description

@migeed-z

Describe the Bug

aliases_variance.py, generics_variance.py and protocol_variance.py

Sandbox Link

No response

(Only applicable for extension issues) IDE Information

No response

Activity

  1. self-assigned this
    on Jan 29, 2026
  2. stroxler commented on Jan 29, 2026

    @stroxler
    Contributor

    @migeed-z I tagged as P1 for now, but maybe there should just be a P0 epic for variance stuff, it does seem like it needs work in a v1 release

  3. added this to the V1 Release milestone on Jan 29, 2026
  4. added
    epicAn issue that is an umbrella for work tracked in other issues
    on Jan 30, 2026
  5. added theissue type on Jan 30, 2026
  6. migeed-z commented on Feb 1, 2026

    @migeed-z
    ContributorAuthor

    @migeed-z I tagged as P1 for now, but maybe there should just be a P0 epic for variance stuff, it does seem like it needs work in a v1 release

    This is a much bigger problem than I thought! ideally, we want a warning mode, a checking mode and our inference mode. This will need additional plumbing so we can reuse as much of the machinery as possible but configure it with different settings.

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

Metadata

Metadata

Assignees

Labels

epicAn issue that is an umbrella for work tracked in other issuestypechecking

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions