Steven Fackler

That either requires us to guarantee that the __type field comes first in the serialized form, which can be hard to enforce through various layers of glue, or buffer all...

Rust implementation: https://github.com/palantir/conjure-rust/commit/181e0a665c0d0c20de7866889dda7d873eb25f60

The motivation is that we have endpoints on an internal service that don't behave like a POST or PUT, but more like a PATCH. Why would Conjure define the format...

I don't understand your question. There is no non-HTTP target for Conjure at the current time AFAIK.

JSON patch was definitely designed with the PATCH HTTP method in mind, but I disagree that it's the canonical thing to use with it. Its RFC says that it "is...

Follow up note here - conjure-rust does now support these types, but via a bit of a gross API and I think they're semantically a bit iffy in general due...

It is in conjure-java's example service, which is where I noticed it: https://github.com/palantir/conjure-java/blob/develop/conjure-java-core/src/test/resources/example-service.yml#L162 Probably worth logging a deprecation warning at least if we want to get rid of it?

How are we going to handle the serialization/deserialization in Jackson, since we need SafeLong to continue serializing as a number and normal longs to serialize as strings?

Handling the serialization in conjure-rust requires a bit of hackery, but it's dooable: https://github.com/palantir/conjure-rust/pull/20

The internal service that I work on uses 64 bit integers as timestamps in its API. Safelongs aren't sufficient since 2^53 nanoseconds is only ~104 days. We don't expect any...