Skip to content
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

is_finiteorder -> is_finite_order #1639

Merged
merged 1 commit into from
Mar 22, 2024

Conversation

joschmitt
Copy link
Collaborator

I think is_finiteorder is against the naming conventions? While I'm at it: shouldn't it be has_finite_order?

Copy link

codecov bot commented Mar 20, 2024

Codecov Report

Attention: Patch coverage is 33.33333% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 86.76%. Comparing base (9ab3cbf) to head (44958b6).

Files Patch % Lines
src/Groups.jl 33.33% 2 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1639   +/-   ##
=======================================
  Coverage   86.76%   86.76%           
=======================================
  Files         114      114           
  Lines       29693    29693           
=======================================
  Hits        25763    25763           
  Misses       3930     3930           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@benlorenz
Copy link
Collaborator

I think it would be better for Oscar to make an alias for now and do the deprecation later?

@joschmitt
Copy link
Collaborator Author

I think it would be better for Oscar to make an alias for now and do the deprecation later?

Yes, I wasn't sure whether this would break OSCAR but unfortunately it does.

Copy link
Member

@fingolfin fingolfin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am for this change, and in fact we discussed it when breaking away for GroupsCore but for various reasons decided to do it later (and then forgot, I guess).

Of course it should be done in a way that maximizes compatibility / minimizes (or better: avoids) breakage.

However, I thought @alias would do that, and in fact OscarCI tests pass, so what is the problem?

Copy link
Collaborator

@benlorenz benlorenz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem anymore, when I made my comment it was realized as a deprecation (https://github.com/Nemocas/AbstractAlgebra.jl/compare/55fcbc8a86e68ab49406fc7cc5b2a1d505ea55a0..44958b69cdf32ece70510fd5edac2ed91c897e97) but that is changed now.

@lgoettgens lgoettgens merged commit a83e8b8 into Nemocas:master Mar 22, 2024
29 of 30 checks passed
@joschmitt
Copy link
Collaborator Author

Too late, but what about the is_finite_order vs has_finite_order?

@joschmitt joschmitt deleted the js/finiteorder branch March 22, 2024 08:50
@lgoettgens
Copy link
Collaborator

lgoettgens commented Mar 22, 2024 via email

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.

4 participants