bumping aeson and making compilation work

[L0neGamer]

No description provided.

[facebook-github-bot]

Hi @L0neGamer!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[L0neGamer]

I have done the CLA now.

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks!

[adinapoli]

Not a maintainer, but my unsolicited review:

• Arguably this could be made DRYer by having a single .Compat module where the CPP is hidden, rather than replicating the same fix all over the place;
• KeyMap has a Monoid instance, so you could replace those KM.empty with simply mempty which I think should work for older versions of aeson (defaulting to the HashMap instance);

@chessai This is not perfect but it would be nice to merge it (even if it means a follow-up is needed to clean it up), as it would be extremely nice to have the aeson-2 story under control.

(I'm available to shepherd this issue, if needed, as such patch would benefit my work as well).

[L0neGamer]

@adinapoli Hi, I made the changes as requested, and as a result everything looks much nicer.

[adinapoli]

Great! I'm happy that my suggestions turned out to be useful. As said before, unfortunately I'm not a project maintainer, but I hope somebody will be able to review this one properly soon.

…

On Sat, 23 Dec 2023, 12:05 L0neGamer, ***@***.***> wrote: @adinapoli <https://github.com/adinapoli> Hi, I made the changes as requested, and as a result everything looks much nicer. — Reply to this email directly, view it on GitHub <#724 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADL5M3N5I7XFNHB34YTZPLYK23JBAVCNFSM6AAAAAA5ASP3FOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRYGI3TAMBZG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[L0neGamer]

@chessai may I ask for a review?

[L0neGamer]

Maybe @stroxler can review?

[facebook-github-bot]

@stroxler has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.