Almann Goo

Define the model/API around typing Macros and how they map to an Ion 1.1 module. What is not in scope here is how the local macro table is set up--that...

Users generally will work only with `IonReader`, but _within_ the implementation it may be useful to operate generically across different `IonReader` implementations. E.g., I have an abstraction that works across...

Strongly Typed Element Views

7

When discussing how `Value` and the _content_ within `Value works in #500, we discussed adding typed views over `Element`. Having typed views as distinct types can allow a user to...

As a user, it would be nice to be able to iterate over any `Element` as though it were a collection. The typical use case is that something is a...

When investigating https://github.com/partiql/partiql-lang-rust/issues/43, I noticed a couple of things. the `max_container_depth` option: https://github.com/amzn/ion-c/blob/d63172996beb043cc06f8a626517eac40ea2699d/ionc/include/ionc/ion_writer.h#L66-L69 Is basically never used. Furthermore, the default of `10` can easily be overrun, and probably should be...

Ion Reader Fails with Assertion on Empty Buffer Read

1

Attempting to read a `clob` or `blob` with a zero byte buffer fails with assertion: ``` ionc/ion_reader.c:1747: _ion_reader_read_lob_bytes_helper: Assertion `buf_max' failed. ``` This should not happen especially if caller code...

By default, the CLI tools (both `ion` and `ionizer`) have very small buffers for various things. A customer had a file, for example with a 90K byte string literal in...

Timestamp Parsing of YY-MM-DDT Fails As Invalid

1

The following test fails: ```c++ TEST(IonTimestamp, YYMMDDT) { ION_TIMESTAMP timestamp; SIZE chars_used; std::string lit("2020-08-10T"); ION_ASSERT_OK(ion_timestamp_parse( &timestamp, (char *)lit.c_str(), (SIZE) (lit.size() + 1), &chars_used, &g_IonEventDecimalContext )); ASSERT_EQ(lit.size(), chars_used); } ``` `ion_timestamp_parse`...

When implementing `ion-c-sys` in Rust, I ran into amzn/ion-rust/issues/#79. Specifically, this API appears to return `nan` for at least the following `ION_INT` values: ``` 57516904150035820771702738217456585 77008733801862767698341856677462573 4623874712756984956766514373293465450 9970304500552494301196940956407522192 59025723530133359201873978774331457987 19141033431585215614236049655094977149...

As per amzn/ion-rust#80, there appears to be no way for an end user to construct an `ION_DECIMAL` from an `ION_INT` using [`ion_decimal.c` L287-L293][1]. This API should not require the caller...