-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to merde_json
#196
Comments
Hi Amos! Big fan of your blog, by the way. Actually just stumbled upon merde_json yesterday on one of your Mastodon posts and added it to a project I'm working on. I'd love to work on this! |
That’d be great! I’m not actively working on this yet, I’ll happily review a PR migrating one or both of the use cases to it! |
Awesome! I'll do both :) |
Hey Amos! Full disclosure, trying to do this migration made me rage-quit writing Rust for a bit and I've been slowly working my way back. |
Oh no! That's the opposite of what I'm trying to do overall! It's entirely possible that merde doesn't quite support the features needed by loona right now! I've also been making big changes to merde in parallel, which is fine if I'm the one migrating loona to merde but not if you are x) Apologies for the frustration — feel free to open a draft PR so your in-progress work is visible somewhere, and let me know if it's fine to use it when I pick that back up! |
Haha no worries! It just showed me how much I still need to learn which is a positive outcome. Anyways, I've made a draft PR which I hope will serve as a good starting point when you do eventually migrate. |
(disclaimer: I wrote it)
https://github.com/bearcove/merde_json is lighter than serde_json, and could easily replace it for the two places fluke deals with json:
This is low-priority but it'd also help with compile times overall so.
The text was updated successfully, but these errors were encountered: