Doug Roper

@russellremple was able to reduce quite a bit of the penalty when he ported the upickle 3 macros to weepickle in https://github.com/rallyhealth/weePickle/pull/81, mostly by removing those runtime Maps. Even so,...

One breaking change to consider is the discrepancy between: ``` def visitFloat64StringParts(s: CharSequence, decIndex: Int, expIndex: Int, index: Int): J def visitFloat64String(s: String, index: Int): J ``` I haven't investigated...

There might be something useful that can be ported over from https://github.com/rallyhealth/weePickle/pull/94.

The proposed change makes sense to me. We took this a step further in https://github.com/rallyhealth/weePickle/pull/77 by making `SimpleVisitor` throw on `visitNull` so that even reference types are null-hostile unless overridden....

Here's a start to mimic weepickle's all-or-nothing null handling: https://github.com/com-lihaoyi/upickle/commit/c301c6e6e8cd1429f67f23743d5dd184ff0abd27. I'm stopping short of submitting a PR since: 1. It introduces complexity. 2. It doesn't support targeting only primitives, i.e....

Looks like this just affects ujson's AST. Workaround: the http://www.lihaoyi.com/upickle/#OtherASTs probably handle it properly. I know play-json represents all numbers as `BigDecimal`. https://tools.ietf.org/html/rfc8259#section-6 and https://tools.ietf.org/html/rfc8259#section-9 indicate that parsers may reject...

Would be nice for @lihaoyi to weigh in. If this limitation is intentional, seems to me like it should be documented somewhere.

Similar to #1153.

Similar to #1153.

I've implemented both of those `InMemoryStubMappings` optimizations locally. The speedups are significant. Short-circuiting on `isExactMatch` is pretty trivial to implement for the gains. I just replaced [this](https://github.com/wiremock/wiremock/blob/89907f038162f059ec98f8f812831bc6b5c12f44/src/main/java/com/github/tomakehurst/wiremock/matching/RequestPattern.java#L96-L105) with `schemeMatches().isExactMatch &&...