-
Notifications
You must be signed in to change notification settings - Fork 246
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
Algebra.Bundles.SemiringWithoutOne
fails to export setoid
?
#1917
Comments
Aaargh, this issue is really two:
The first might be easy (but I feel faint thinking about it), but the second? |
[deleted] |
I now find myself in the uncomfortable position of having a solution, but one which I do not understand, and hence don't know if it will cause problems later if merged... :-( UPDATED: the issue/diagnosis on the PR is that |
Looks like a bug to me. Report on the Agda repo? |
Hmm, resolved after an |
More specifically,
Algebra.Bundles.Semiring
does indeed export all of its corresponding substructures (down tosetoid
derivable viaAlgebra.Structures
), whileAlgebra.Bundles.SemiringWithoutOne
appears not to. Not quite sure how to fix this, but will update if/when I do... with a minimum (non-)working example.EDITED: See the two
Test
files atAlgebra.Properties.Semiring{WithoutOne}
on this branch now minimised.UPDATE: the problem seems similar to that described/solved in issue #1159 / PR #1174, and I think I have a solution, but I'm conscious of being out of my depth as to the arcane define/public re-export structure of the
Algebra.*
hierarchy, so reluctant to issue a PR about this... Which raises a separate question: how 'high' (=fewest operations, axiomatic properties) in theStructures
(and henceProperties.BundleX.OperationY
) hierarchy do we want certain things to live: eg distributivity of_*_
oversum
, defined in #1462, placed it as a property ofSemiring
s; @uzytkownik 's original contribution (from a year earlier) under #1287 placed it underSemiringWithoutOne
... and AFAICT, it doesn't even need that much structure, only that of the theory pullback (which has no name) ofSemiringWithoutOne
andSemiringWithoutAnnihilatingZero
. In pursuit of #1287, I'd be happy for everything to live under properties ofSemiring
, and leave the appropriate weakening of structure to subsequent refactoring... but I know that there are strong views about the ambient guiding principle of 'be no less general than you absolutely can', and I thought that this was worth flagging.The text was updated successfully, but these errors were encountered: