You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am considering using this crate to use YAML instead of pure JSON for the configuration files of one of my projects, but am not sure what to think about the use of unsafe-libyaml... Safety is a big concern for us and this effectively introduces a bunch of unsafe code responsible for parsing arbitrary input.
Looking at the history I see that yaml-rust was used previously, but seems to have been abandoned in favor of unsafe-libyaml due to lack of maintenance. That's unfortunate but the decision is understandable.
Are there other alternatives that could be used to parse YAML? Or are my concerns about unsafe-libyaml unwarranted?
The text was updated successfully, but these errors were encountered:
Hi and thanks for this very useful crate.
I am considering using this crate to use YAML instead of pure JSON for the configuration files of one of my projects, but am not sure what to think about the use of
unsafe-libyaml
... Safety is a big concern for us and this effectively introduces a bunch of unsafe code responsible for parsing arbitrary input.Looking at the history I see that
yaml-rust
was used previously, but seems to have been abandoned in favor ofunsafe-libyaml
due to lack of maintenance. That's unfortunate but the decision is understandable.Are there other alternatives that could be used to parse YAML? Or are my concerns about
unsafe-libyaml
unwarranted?The text was updated successfully, but these errors were encountered: