Classify each IDL symbol into its optional type family#28
Open
estebanzimanyi wants to merge 1 commit into
Open
Classify each IDL symbol into its optional type family#28estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
Derive a family field for every function, struct, and enum from the declaring header's canonical location: the meos/include/<family>/ subdirectory, or the top-level meos_<family>.h public header, falling back to CORE for the temporal core, the base geo/tpoint types, and the shared top-level headers. A binding gates a family in or out purely by this field, so an edge build can drop unused families such as POINTCLOUD to shrink its footprint.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Derive a family field for every function, struct, and enum from the declaring header's canonical location: the meos/include// subdirectory, or the top-level meos_.h public header, falling back to CORE for the temporal core, the base geo/tpoint types, and the shared top-level headers. A binding gates a family in or out purely by this field, so an edge build can drop unused families such as POINTCLOUD to shrink its footprint. The classification covers all ten optional families (CBUFFER, NPOINT, POSE, RGEO, H3, QUADBIN, POINTCLOUD, JSON, ARROW, RASTER); a regression test asserts each is populated, that representative symbols land in the right family, and that the temporal core stays CORE.