-
Notifications
You must be signed in to change notification settings - Fork 2
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
unserialize_config: section read as keyval #23
Labels
Comments
This problem is currently limited by a design flaw that does not allow an element to receive operations designed for the other element type. Therefore, we are not able to reliably fix this issue in the current implementation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What should be the behavior of dc_finalize on a keyval when its mold equivalent is of type section
and dc_fatal_error is called with context (context keyval is in fatal state).
Came across this when testing unserialize_config, and as of now finalize returns
context in wrong state, which is expected. However, in order to recover and present such an
error wouldn't it be better if a context of wrong type whose root context is of type config is allowed to
be finalized. That is, with a name and the error INVALID_CONTEXT is return from dc_finalize?
The text was updated successfully, but these errors were encountered: