Prevent `write` and `display` from quoting operators in sexps

[toddjonker]

ionize does not quote operators in sexps, but write does. The former is preferable.

**$ (ionize (quote (+ 1 2)))

(
+
1
2
)
$ (write (quote (+ 1 2)))
('+' 1 2)$**

The implementation of ionize delegates to IonWriter, which tracks quoting context, but write does its own thing and loses that context. I'm not exactly sure how to track that flag.

Similarly, display special cases string and symbol but otherwise delegates to write, so fixing the latter will also fix the former.

[DimitriosDalaklidhs]

I can see that ActualSymbol.write() calls IonTextUtils.printSymbol() which loses sexp context, while ionize delegates to IonWriter which tracks it. Would the fix involve threading a context flag through Evaluator, or is there another mechanism you had in mind for tracking whether we're inside a sexp during write?

[toddjonker]

There ultimately needs to be a mechanism for the rendering of a particular value to determine whether the context requires operator quoting. I've stating that requirement as a generalization since IMO the ideal solution would be generalized.

This ticket specifically concerns the situation where the context is "immediate parent is rendering as an sexp", in which case operator quoting is usually undesirable.

Note that the current behavior is not incorrect: it's still valid Ion format with equivalent semantics. It's just less human friendly, and not the best default behavior.

[toddjonker]

It just now occurred to me that this issue also affects display, so I'll update.

[toddjonker]

Sorry, I'll answer your question more directly

Would the fix involve threading a context flag through Evaluator, or is there another mechanism you had in mind for tracking whether we're inside a sexp during write?

It doesn't need to go through the Evaluator just through the internal write implementation metheds I point out in my comments on #490