You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should revisit this topic when we label Decapodes with the calculus it comes from using types, since there may be value then in detecting such mal-formed types at parse-time. AlgebraicJulia/DiagrammaticEquations.jl#19
For example, if I say that my equations are written in the 1D DEC, then there is value in throwing a parsing error when I try to use a 2-Form.
Currently, we check that the types are a 0-Form, 1-Form, etc., and raise an error if a type is e.g.
VectorField
when we are parsing.Since:
We should move this check to somewhere inside
gensim
.The text was updated successfully, but these errors were encountered: