@decapode not usable in source

[lukem12345]

Attempting to define a particular Decapode in any source file (of the DiagrammaticEquations package) causes a segmentation fault.

To reproduce:

1. Go to any source file, such as src/language.jl
2. Define a decapode. e.g.

g = @decapode begin
  A == B + C
end

3. Open a REPL. Do using DiagrammaticEquations, DiagrammaticEquations.Deca. Attempt to construct a Decapode using the @decapode macro. This causes a segmentation fault.

[lukem12345]

@jpfairbanks Is this an intertypes thing?

[lukem12345]

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

[lukem12345]

Segfaults on 9bbe494
Does not segfault on e4df0b6

[lukem12345]

@quffaro Can you take a gander at this and see if this is an issue for ACSets.jl?

[quffaro]

@lukem12345 I was able to replicate the issue. Thank you for the helpful analysis! I'll look at the two commits you posted

[jpfairbanks]

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.

[lukem12345]

This issue should be closed upon completion of upcoming PEG PR associated with #88

[lukem12345]

After reconsidering, #88 won't fix this, because it just changes the parser, but still uses the Decapode ACSet.

A simple way of resolving this issue is to move intertypes related code into the tests, where we can just verify that the DecapodeACSet from src is compatible.

[jpfairbanks]

I think we could also add an extra module that wraps the intertype's and then re-export that functionality

[lukem12345]

@jpfairbanks Tried this simple nesting structure but it failed. What nesting pattern do you mean?

main...refs/heads/llm/wrap_it

https://github.com/AlgebraicJulia/DiagrammaticEquations.jl/actions/runs/14541165472