Todd V. Jonker

Results 40 issues of Todd V. Jonker
trafficstars

>Now that you mention it, I feel icky about ignoring annotations. That seems likely to lead to users of the macro being surprised by data-loss. > > We could use...

specification 1.1

For pedagogical intentions, the 1.1 book covers topics in more than one place. We have the "by example" chapters that cover things with a narrative and incremental manner, the (currently...

documentation
specification 1.1

E-expressions have shorthand `(:)` when expressing void arguments, but at present templates must use the more-wordy `(void)`. List tradition seems to generally avoid treating `()` as a valid expression form,...

enhancement
specification 1.1

Capturing a TODO from #249

enhancement
specification 1.1

Relevant discussion at: * https://github.com/amazon-ion/ion-docs/pull/249/files#r1222125668

enhancement
specification 1.1

[Follow-up to #240] I'm becoming inclined to ditch the `!` modifier altogether. It's only used in conjuction with simple tagged params, it'll probably never be used, and its presence seems...

enhancement
specification 1.1

As [noted](https://github.com/amazon-ion/ion-docs/blob/f2db864a645fff711f9874588ae0e294c717e983/src/binary-encoding.adoc?plain=1#L2289) in the binary encoding chapter: > * Do we need a `compact_string` encoding? It saves a byte for string lengths >16 and

documentation
specification 1.1

Among my TODOs noted in #219: * I'm increasingly dissatisfied with the long comparison with symbol table directives. Would be better to start fresh here and cover legacy concerns in...

documentation
specification 1.1

I can't think of a use case where we would want to _silently_ drop the end of the longer stream, and so being able to see that there are more...

specification 1.1

We've got a couple varieties floating around, most recently `compact_*` which is quite good. Would love to find something just as good that's a couple characters shorter though. Regardless, we...

documentation
specification 1.1