We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The documentation for complex claims:
complex
This constructor minimizes computation and does very little error checking. To verify that a complex is well constructed, use isWellDefined(Complex).
However, when defining a complex it seems the source and targets are held to a higher standard than chainComplex:
chainComplex
i1 : needsPackage "Complexes"; i2 : R = QQ[x,y]; i3 : complex { matrix {{x, y}}, matrix {{-y}, {x}} } stdio:3:7:(3): error: map with index 2 has inconsistent target i4 : chainComplex { matrix {{x, y}}, matrix {{-y}, {x}} } 1 2 1 o4 = R <-- R <-- R 0 1 2 o4 : ChainComplex
Is there a reason why the targets are not adjusted on the fly similar to chainComplex?
i5 : target o4.dd_2 === source o4.dd_1 o5 = true
cc: @mikestillman @ggsmith
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The documentation for
complex
claims:However, when defining a complex it seems the source and targets are held to a higher standard than
chainComplex
:Is there a reason why the targets are not adjusted on the fly similar to
chainComplex
?cc: @mikestillman @ggsmith
The text was updated successfully, but these errors were encountered: