Timo Meijer

This does not have to do with circe-yaml, but with the circe Decoders. This functionality is already available, for reference see: https://circe.github.io/circe/codecs/custom-codecs.html#custom-key-mappings-via-annotations

@zmccoy @jeffmay Would you have time to take a look? Thanks!

I can see if I can reproduce this locally tomorrow, and if so, investigate further

The compile error actually occurs in both 2,12 and 2.13, but not in 3. If I change the package object into a regular object, the error disappears. I have not...

Minimal example of the behavior: https://gist.github.com/TimoMeijer/bef21c11cb13fa283205de1dd32347d2

@zmccoy Would it make sense to split the implementation of parser between 2.x and 3.x, as we can support this behavior on 3.x already? Or would we not want to...

Thanks for your thoughts @jeremyrsmith! My original case was that I wanted to use `decodeAccumulating` with yaml files. On looking into it further, I noticed it was implemented on the...

@som-snytt Thanks for digging that up! That made me test a couple more Scala versions, to check whether this specific behavior has ever functioned correctly, but from my investigation it...

Thanks! I'd be happy to help, but have never contributed or looked into the scala compiler before, so I wouldn't know how to begin. And indeed, the entire point seems...

This is apparently undefined, from the spec(https://github.com/scala/scala/blob/2.13.x/spec/09-top-level-definitions.md): ``` The package object should not define a member with the same name as one of the top-level objects or classes defined in...