-
Notifications
You must be signed in to change notification settings - Fork 1
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
@decapode not usable in source #74
Comments
@jpfairbanks Is this an intertypes thing? |
Following the above steps on commit 88b1874 , no segfault occurs and everything runs as expected. I'll keep bisecting and see what might have introduced this. Hopefully it is something related to Revise.jl or some such |
@quffaro Can you take a gander at this and see if this is an issue for ACSets.jl? |
@lukem12345 I was able to replicate the issue. Thank you for the helpful analysis! I'll look at the two commits you posted |
I bet this has to do with the fact that we don't put the Decapodes ACSet types into their own submodule. So there is no module boundary between code that is in a src/x.jl file and the code that defines the types. The tests and docs both live in modules that import DiagrammaticEquations rather than directly live inside it. So we can create decapodes outside that module, but not within it. Hopefully the only fix we would need is to wrap any intertypes generated type with a submodule of the package. |
Attempting to define a particular Decapode in any source file (of the DiagrammaticEquations package) causes a segmentation fault.
To reproduce:
src/language.jl
using DiagrammaticEquations, DiagrammaticEquations.Deca
. Attempt to construct a Decapode using the@decapode
macro. This causes a segmentation fault.The text was updated successfully, but these errors were encountered: