-
Notifications
You must be signed in to change notification settings - Fork 77
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
Control.Concurrent.STM.atomically was nested #86
Comments
Hmm... I looked into this a bit more. I think it's the |
I'm guessing rewriting |
Actually, there's probably a better solution available: modify |
Sure, I can give it a go.
|
Can you confirm that this issue does not exist with the newly released enclosed-exceptions version? |
Closing as believed to be fixed. |
yaml < 0.8.22 causes literate-unitb-logic's test suite to throw an exception: Control.Concurrent.STM.atomically was nested Possibly related: snoyberg/yaml#86 Not sure about the exact cause, but we don't seem to have the issue with yaml >= 0.8.22, so I'm bumping the lower bound as a workaround.
Swap out ConfigFile for yaml * [1/4] Swap out ConfigFile for yaml Config file's name changed from z3_config.conf to z3_config.yml. TODO: there's a slight issue with the yaml library treating all of Z3Config's fields as String, in that it will require the numbers to be explicitly quoted to be considered as string literals; and otherwise it will ignore them. We'll try to fix this by generalizing the Document type class and the functions using it. * [2/4][WIP] Generalize Document * [3/4] Generalize Document (cleanup) - literate-unitb-config compiles again - Add traverseOf (similar to lensOf and prismOf) - Swap `fieldWith`'s arguments to make them consistent with `field` * [4/4] Rename unitb-option executable to unitb-config * Pin yaml to >= 0.8.22 to avoid issue with STM yaml < 0.8.22 causes literate-unitb-logic's test suite to throw an exception: Control.Concurrent.STM.atomically was nested Possibly related: snoyberg/yaml#86 Not sure about the exact cause, but we don't seem to have the issue with yaml >= 0.8.22, so I'm bumping the lower bound as a workaround. * Clean up comments * Align =>, ->, and :: properly
foo.hs:
result:
Uh...? I don't believe this is actually a
yaml
bug because it doesn't depend onstm
, but one of its dependencies, somewhere, is calling someunsafePerformIO (atomically foo)
-type thing. Not too sure where to look from here.The text was updated successfully, but these errors were encountered: