-
Notifications
You must be signed in to change notification settings - Fork 26
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
Standard Library: INI, YML/YAML #538
Comments
This really should be 3 issues instead of 1.
|
INI is too common of a format. There is going to be versions of it we can't support because of the lack of specification — there's some really cursed ones out there — but I'm fine with TOML alongside it. This is fine as one issue too, it's all solutions working towards one major problem: the lack of data format parsers (minus json). |
If you're fine with not being able to support "all versions of it", then I think you'd be fine with adding TOML instead of INI. We could document it as "TOML/INI" so users will know what's up. |
Upon further investigation, it seems TOML is not a superset of INI as I initially thought. Of course, we'd still have the issue of many INI dialects existing in the wild, but I hope some configurable options can address that. |
No description provided.
The text was updated successfully, but these errors were encountered: