buildingSMART / buildingSMART/NextGen-IFC
Ensure that SELECT entities only contain somewhat equivalent data types
Open
enhancement
- Dominant language
- TeX
- Stars
- 64
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I suggest ensuring that the EXPRESS data types included in SELECTs are equivalent in kind. EXPRESS allows mixing ENTITY, SET, STRING, and anything else into one SELECT, but this creates awkward structures in any other language.
There are a few examples / few cases. #19 is one of them.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.