Essentially: Does combination of the MemoryPool<char> and various buffer size hints on Options and the configurable steps of (de)serialization wrapped in (De)SerializableMembers (and associated types like InstanceProviders, Setters, Formatters, etc.) provide sufficient control over when and how allocations happen?
Put another way, is there any place where using Cesil currently requires allocations that a consumer cannot influence or control either the timing or manner of those allocations?
This is an Open Question, which means:
[A]s part of the sustainable open source experiment I detailed in the first post of this series, any commentary from a Tier 2 GitHub Sponsor will be addressed in a future comment or post. Feedback from non-sponsors will receive equal consideration, but may not be directly addressed.
This was posed in Overthinking CSV With Cesil: “Maximum” Flexibility.
Essentially: Does combination of the
MemoryPool<char>and various buffer size hints onOptionsand the configurable steps of (de)serialization wrapped in (De)SerializableMembers (and associated types like InstanceProviders, Setters, Formatters, etc.) provide sufficient control over when and how allocations happen?Put another way, is there any place where using Cesil currently requires allocations that a consumer cannot influence or control either the timing or manner of those allocations?
This is an Open Question, which means: