Skip to content

Conversation

@brunoabinader
Copy link
Member

@brunoabinader brunoabinader commented Nov 30, 2018

Given that the data source for generating the properties map doesn't change after the feature object is instantiated, this PR:

  • Generate properties map upon first call, then store it for further getProperties() calls
  • Return properties using pass-by-const-ref to avoid extra copies
  • Use getProperties() logic in getValue()

kkaefer and others added 18 commits June 2, 2017 15:02
…peated uses of this tactic to allocate and leave multiple vectors, shifted max reserve from 10mb to 1mb.
Prevent Massive Over Allocation
Align property parsing with JS implementation
… y position if multiple int32_t deltas push a value outside of the max range of an int32_t. This change bumps the x and y values to int64_t. It is still possible to have an overflow or underflow, however, this is much less likely and would require a large number of large deltas to reach this point.
Preventing Overflows and Underflows on Points
It seems that the QNX 7 compiler (i.e qcc based on GCC 5.4.0 with
libc++ from LLVM) has a limited c++11 feature support and causing
compilation errors with the inheriting constructors. This patch
fixes the issues by providing the universal forwarding constructor.
Also, resolves an ambiguous overload error with optional<T>.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants