Skip to content

Pixie related code still in Genny #21

Closed

Description

@chrisheller

Just took a quick perusal of this. Looks great.

I did notice that there are a few places where there is some Pixie related code still hanging around though. For example, in the exportObjectNim proc in genny/languages/nim.nim, there is a hard-coded check for some Pixie related types (Vector2, Matrix3, etc.)

genny/languages/python.nim also has this (e.g. mapping Vec2 to Vector2 in exportTypePy).

I'm guessing that is just from the re-factoring to split Genny out of Pixie and into its own project though.

Activity

  1. guzba commented on Sep 14, 2021

    @guzba
    Collaborator

    Yep that is correct. We're removing hard-coded bits like this as we add a means to accomplish the same thing within the Genny DSL. We still need to sort out some type name re-mapping stuff and also errors (PixieError is hardcoded iirc). These will be sorted soon.

  2. treeform commented on May 25, 2026

    @treeform
    Owner

    I have removed the Pixie-specific hardcodes from Genny’s generator code. Genny now derives these bindings from the binding files, including tricky external/value types such as Vec2 and Mat3 from vmath, plus simpler types like Rect and Color. Pixie is still used extensively as a test fixture, but the generator itself no longer has Pixie-specific code paths.

    #67

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions