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
There are only four different types of TimeType possible and two different types of IntervalType[*]. Instead of creating new ones from imported or deserialized values, these can just be interned -- reducing GC pressure ever-so-slightly.
(It would also be possible in principle to TimestampType but the timezone complicates that a little.)
*Well, there could also be MONTH_DAY_NANO once a newer version of the FlatBuffers is imported... .
Component(s)
C#
The text was updated successfully, but these errors were encountered:
### What changes are included in this PR?
A small refactoring to make a small improvement in memory utilization.
### Are these changes tested?
Existing test coverage should be sufficient.
* Closes: #36816
Authored-by: Curt Hagenlocher <curt@hagenlocher.org>
Signed-off-by: David Li <li.davidm96@gmail.com>
### What changes are included in this PR?
A small refactoring to make a small improvement in memory utilization.
### Are these changes tested?
Existing test coverage should be sufficient.
* Closes: apache#36816
Authored-by: Curt Hagenlocher <curt@hagenlocher.org>
Signed-off-by: David Li <li.davidm96@gmail.com>
Describe the enhancement requested
There are only four different types of TimeType possible and two different types of IntervalType[*]. Instead of creating new ones from imported or deserialized values, these can just be interned -- reducing GC pressure ever-so-slightly.
(It would also be possible in principle to TimestampType but the timezone complicates that a little.)
*Well, there could also be MONTH_DAY_NANO once a newer version of the FlatBuffers is imported... .
Component(s)
C#
The text was updated successfully, but these errors were encountered: