Skip to content
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 libyaml-safer #5

Open
acatton opened this issue May 26, 2024 · 2 comments
Open

Migrate to libyaml-safer #5

acatton opened this issue May 26, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@acatton
Copy link
Owner

acatton commented May 26, 2024

My goal is to get rid of unsafe {} blocks. I think the Rust community is too aggressive with unsafe {}. I know that it's impossible to avoid when working with C library.

However, I love the initiative from @simonask "libyaml-safer".

I'm hoping to find time to start migrating to it, and clean up all the unsafe blocks in serde-yaml-ng. I'm happy to fix stuff on libyaml-safer if necessary. (this is why I'm pinging Simon on this issue :) )

@acatton acatton added enhancement New feature or request good first issue Good for newcomers labels May 26, 2024
@acatton acatton self-assigned this May 26, 2024
@acatton acatton added this to the 0.15: Cleaned up version milestone May 26, 2024
@simonask
Copy link

Let me know if you have any questions or if there is anything I can do to help out. :-)

@acatton
Copy link
Owner Author

acatton commented May 27, 2024

Absolutely, thank you for your work Simon 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants