Skip to content

Conversation

@msyds
Copy link

@msyds msyds commented Nov 16, 2025

Closes #1251.

This is a very big rename. It would've been much easier to rename isIso's fields to match Iso's rather than the other way around, but I strongly believe that would leave us with an even worse inconsistency.

@msyds
Copy link
Author

msyds commented Nov 16, 2025

The first commit is nothing but the application of a straightforward search-and-replace and does not typecheck. The second commit manually resolves the handful of scope errors introduced and gets everything compiling again. I'm currently combing through the diff to undo any false-positives and will follow up with one last commit }:). By that point, this should be mergable, assuming this is even a welcome change.

@msyds msyds changed the title Resolve inconsistency between Iso and Category.isIso Resolve naming inconsistency between Iso and Category.isIso Nov 16, 2025
@msyds
Copy link
Author

msyds commented Nov 16, 2025

(A few of said false-positives (BiInjective, IsoOver) should probably be renamed to match Iso and isIso anyway, but that can be done in a separate PR.)

@msyds msyds marked this pull request as ready for review November 16, 2025 13:26
@msyds msyds marked this pull request as draft November 16, 2025 15:49
@msyds msyds marked this pull request as ready for review November 16, 2025 16:07
@mortberg
Copy link
Contributor

I have no strong opinions on this, so if @maxsnew thinks it's better I'm fine with merging

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Inconsistency between Iso and Category.isIso

2 participants