Matthew Pope

I talked with @zslayton, and we came up with some requirements that we believe are important for a typed element API. * All structs should be opaque or non-exhaustive so...

I put together a prototype of another idea that I had: https://github.com/popematt/ion-rust/commit/01e4d4a587a0d0421689c25a6e47ef3df50ea8ae This gets us (nearly) free casting between different _concrete_ Element types _and their references_, and I think we...

FYI, I talked to @zslayton earlier this week and forgot to put an update here. The idea that spawned my approach was that with some control over the memory layout...

> I would expect the s-expression `(null+inf)` to be parsed as `( null + inf )`, not `( null +inf )` So, `(null+1)` seems like it's pretty clear that it...

Is this referring to Ion 1.0 or the Ion 1.1 proposal (or both)?

It does look pretty trivial (unless, perhaps, you're encoding lots of floats in a tight loop). We should see if there's a significant performance difference in Java (and maybe some...

@zslayton, I'm going to close this as completed. Feel free to re-open if you disagree.

> We agreed to delay implementation of parameter cardinality, not eliminate it. (As I work on the denotational semantic model, I'm becoming more convinced that we need more strong typing,...

Another way of putting this is that `values` is such a fundamental piece in the macro system, that it deserves to have its own syntactical sugar.

A syntax for streams would only add confusion unless expression groups, streams, and the `values` macro can be unified. There is no inherent issue preventing these concepts from being merged,...