Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enumerate issues with Unittests #76

Open
sildeag opened this issue Apr 19, 2018 · 0 comments
Open

Enumerate issues with Unittests #76

sildeag opened this issue Apr 19, 2018 · 0 comments

Comments

@sildeag
Copy link

sildeag commented Apr 19, 2018

Many of the unittests currently seem to fail with the MTG/gaia build. The source seems to be attempted enumeration of RealType. Is this a well known issue, with a fix, work around, or other solution? PointLayout is by design imutable - my understanding is there are three types of variables in a PointLayout: Real, String, and Enum further subdivided into fixed and variable length. Because PointLayout is imutable it means enumeration only works when no Points are added. Is this intended or not or just a mis-impression? There seems to be nothing to switch off attempted enumeration of types other than String, which could be done in descriptortree.cpp without violating the imutable property of PointLayout and without generating an exception message. What is type Enum type used for? Can anyone provided greater insights so that either the unittests can be changed or the code can be fixed so that they all pass if the behaviour is as expected?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant