-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimize buffering w/ v1.1 Binary writer? #884
Comments
You can call Here's the type that holds all of the currently available options: ion-rust/src/lazy/encoder/value_writer_config.rs Lines 1 to 15 in 4e8739f
Each of those enums are defined just below it. Let me know if I can answer more questions. |
Thanks, @zslayton. That's not present on type IonWriter = Writer<v1_1::Binary, File>;
pub struct Log {
ion_writer: IonWriter,
}
...
error[E0599]: no method named `with_delimited_containers` found for struct `ion_rs::lazy::encoder::writer::ApplicationValueWriter` in the current scope --> src/uilog.rs:418:67
|
418 | let mut entry_writer = self.ion_writer.value_writer().with_delimited_containers();
| ^^^^^^^^^^^^^^^^^^^^^^^^^ method not found in `ApplicationValueWriter<'_, BinaryValueWriter_1_1<'_, '_>>` |
Hmm, it should be there. The source code for those methods is here: ion-rust/src/lazy/encoder/writer.rs Lines 243 to 267 in df7ba6c
Note that it's only implemented for |
When I click on that link, I see this When I look in my impl BinaryValueWriter_1_1<'_, '_> {
...
pub fn with_delimited_containers(mut self) -> Self {
self.value_writer_config = self.value_writer_config.with_delimited_containers();
self
} What am I doing wrong? |
I've been digging through the 1.1 rc10 reference docs to figure out how to configure it to minimized buffering--for example by using delimited sequences. I'm afraid I haven't figured it out, so... how can I configure the v1.1 writer to minimize buffering and other overhead when using both the imperative and Serde serialization APIs?
Thanks!
For context, the prototype so far is:
The text was updated successfully, but these errors were encountered: