Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • P Pyston
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Boxiang Sun
  • Pyston
  • Repository
You need to sign in or sign up before continuing.
  • Pyston
  • src
  • codegen
  • compvars.h
Find file BlameHistoryPermalink
  • Kevin Modzelewski's avatar
    Statically resolve tuple-pack-then-unpack, since we use that for LANDINGPAD · b4e3ede1
    Kevin Modzelewski authored Jan 20, 2015
    This seems like a cleaner way to allow type-specific codegen -- make
    all types by default defer to UNKNOWN's handling of unpack().  Override
    the unpack() method in [Unboxed]TupleType to do the unpacking statically
    if possible.
    b4e3ede1
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7