Travis Brown

The primary argument for the current behavior being the default is that JavaScript does terrible things with JSON numbers (`JSON.parse("1e309")` is `Infinity`, `JSON.parse("1.0000000000000001")` is `1`, etc.), so it's pretty common...

Thanks for opening this issue! One thing to note is that you already get reasonably fine-grained error locations for key decoding failures while decoding a `Map`, as well as error...

@plokhotnyuk Yes, agreed for sure on the security documentation—will work on this soon.

Circe doesn't make any guarantee that every codec will round-trip all values through the JSON representation, even for codecs provided in implicit scope (although the only other examples I can...

I can't answer in detail at the moment, but there was some recent discussion on Gitter that might be relevant: https://gitter.im/circe/circe?at=5f362090aecae32e8ec0c7d6

The [JSON spec](https://www.json.org/json-en.html) doesn't support numbers that start with a decimal point, so I'd consider this out of scope, but you could always hack together a version of Jawn and...

The fact that the number decoders accept JSON strings is mostly a convenience for Scala.js users who don't have support for proper non-double JSON numbers, and these decoders treat numbers...

@darkfrog26 I'm not sure circe will ever support multi-valued keys (although I've considered it), but one much easier solution would be to have a special parser that would parse this...

There are a couple of arguments for the current behavior: - It's just what people tend to expect from a JSON library. - We want to be able to round-trip...

@oscar-broman We don't have any configuration like that, and I think that's a good thing. There's a standard way in Scala to override the behavior of type class instances, and...