Carter Kozak
Carter Kozak
Hi, I'd like to provide a pool of constant-sized byte-buffers rather than using cached byte-arrays that are less configurable and expensive to grow. This would allow me to reuse an...
==COMMIT_MSG== NON-NLS more difficult example ==COMMIT_MSG==
This allows us to avoid class loading even when order doesn't match the stack due to exceptions caught and pased from a slightly different codepath. This change also includes a...
09e1bae: Avoids allocating new string objects when parameters are formatted, preferring to use the existing StringBuilder instance. 38b9650: Remove JsonWriter.formattableBuffer in favor of using the existing JsonWriter.stringBuilder field. from the...
Implemented a new `log4j2.enable.extended.throwable.class.loading` flag which may be set to `false` in order to safely avoid performance pitfalls of class loading.
I've applied some refactors I wrote a while ago: https://github.com/palantir/assertj-automation Separated into two commits, first migrates from other asserts to assertj, and a second which optimizes assertj use.
==COMMIT_MSG== Implement several failing safety-analysis test cases ==COMMIT_MSG== Getting these out of my head, into a system!
## What happened? In some cases it may be possible for nested closeables to skip closing delegates: ```java try (InputStream is = new GZIPInpuutStream(new FileInputStream(file))) { // etc } ```...
## What happened? See the discussion on https://github.com/palantir/gradle-baseline/pull/1670 The change would be fantastic, using immutable collections makes logic easier to reason about, and provides inherent thread-safety. Unfortunately in most places...