Add "accessible" and related notions#59
Add "accessible" and related notions#59ykawase5048 wants to merge 30 commits intoScriptRaccoon:mainfrom
Conversation
93ee1c2 to
ca1b238
Compare
|
Thank you! 🚀 I will have a look at it. I have resolved the merge conflicts (the For future PRs: how comfortable are you with resolving merge conflicts yourself? |
Thanks!
I think I can resolve merge conflicts myself, but I’m not deeply familiar with git, so I would of course be very happy if you prefer to handle them! |
e142cf2 to
49a1025
Compare
|
There is a very interesting issue: It is independent of our foundation, ZFC with two Grothendieck universes, whether the category of free abelian groups is accessible; see [Makkai-Pare, Section5.5] or MathStackExchange. So, we would need to add the third option "undecidable" for properties. |
7e8db08 to
fc57942
Compare
|
Meta comment: I want to finish some other stuff today first. When that is done, I will come back to this PR, answer your comments, and also have a look at all the new commits (thank you!). |
|
Due to the rebase, commits mentioned in the comments may have become outdated. |
|
Minor comment: In this PR, I noticed that the implication "finite" → "small" was incorrect and removed it, which seems to have caused the smallness of several categories to become missing data... |
|
Shall I fix the merge conflicts? |
That's crazy. I have created a separate issue. Let's continue to discuss there. |
My bad! We have "essentially finite => essentially small", right? Generalizing what I wrote in my other comment: when an implication A ==> B is removed, look for all categories where it is not known anymore if they are B, and decide B for them. Either manually or via a new implication. |
acf6993 to
449e5df
Compare
|
I think we can strengthen the implication now, or rather state that Thm. 1.64 in its original form: locally presentable + locally copresentable => thin EDIT. Oh you already did that! Nice. Then ignore my comment. |
|
@ScriptRaccoon |
I have added "accessble" and several related properties:
I had expected that non-accessibility of$\mathbf{Set}^{\mathrm{op}}$ would be inferred automatically, but it wasn’t, so I manually assigned the property. Could this be a bug?