-
Notifications
You must be signed in to change notification settings - Fork 19
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
doesn't work with .gitconfig #8
Comments
(I'm using the version in |
Hi @samoht and thanks for using To.ml. You are right, your gitconfig is compliant with the Toml language, so it's a bug on the 1.0 parser. As we are about to publish a complete rewrite of the parser, I have to ask you if you can upgrade to the last OCaml version or if we have to maintain a backward-compatible 1.0. In the first case, that is: you can upgrade as you will and have no legacy, I will close this issue as it happens on old code. |
Sure, feel free to change the API, I'm not using To.ml in any of my projects (yet). Thanks for the library though, it looks quite useful! |
The git version doesn't compile with OCaml |
It depend of our policy, and for now I'm not sure. For one, we can say that minor versions increment shouldn't break the compilation, but we can also take a more politic view, encourage Opam, and force the dependency on 4.02 because the OCaml world need to move on and managing versions with opam is really dumb easy. It's really just politic at this point, and as @sagotch is the main craftsman of the 2.0, I need his opinion on this topic. |
My point is that then you can't use |
I agree, and the Mirage example is a strong point in favor of being 4.01-compatible. My point is, @sagotch could have reasons to make To.ml depend on 4.02, and I wait for his input before taking any decision. |
discussion on this topic moved to #9 . |
Is that expected?
The text was updated successfully, but these errors were encountered: