You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
, andEnum
further subdivided intofixed
andvariable
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 indescriptortree.cpp
without violating the imutable property of PointLayout and without generating an exception message. What is typeEnum
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?The text was updated successfully, but these errors were encountered: