-
Notifications
You must be signed in to change notification settings - Fork 67
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
Field names for RegularEpi/RegularMono are nondescriptive #341
Comments
I don't have any good suggestions for |
OK, I'm gonna give it a go anyway: we could call them |
It's a bit weird for sure, but consistent with |
At the very least we could go with |
I agree that I'm glad for the suggestions, but I'm not feeling The various reference textbooks that I've checked seem to all go out of their way to not name these! Basically the textbooks all go for a kind of raw Sigma type, but usually drawn as a diagram. Lean's mathlib has a formalization too; they call them 'left' and 'right', which I think is considerably worse. |
On pen & paper, I usually call them as follows:
This underpins the intuition that Unfortunately, this really only applies to |
Currently,
RegularEpi
andRegularMono
are defined like so:Using
h
andg
for the field names here is kind of annoying, as it means that you can'topen
them without renaming, andvariable
blocks inCategory.Morphism.Regular
can't use those names.We should probably pick some better names for these fields, I can't think of anything great beyond
mor₁
andmor₂
. Perhaps others have some insight.The text was updated successfully, but these errors were encountered: