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

make the GapObj in left/right cosets optional #4274

Merged
merged 2 commits into from
Nov 7, 2024

Conversation

ThomasBreuer
Copy link
Member

Compute the GAP coset object only if one asks for it. In particular, do not use it for comparing left cosets with ==.
The implementation is the same as for double cosets, cf. #3899.

This addresses the discussion in #118.

Compute the GAP coset object only if one asks for it.
In particular, do not use it for comparing left cosets with `==`.
Copy link

codecov bot commented Nov 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.50%. Comparing base (19bf27c) to head (3e58354).
Report is 10 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4274      +/-   ##
==========================================
+ Coverage   84.48%   84.50%   +0.01%     
==========================================
  Files         641      641              
  Lines       85447    85488      +41     
==========================================
+ Hits        72189    72238      +49     
+ Misses      13258    13250       -8     
Files with missing lines Coverage Δ
src/Groups/cosets.jl 90.27% <100.00%> (+0.67%) ⬆️

... and 7 files with indirect coverage changes

Comment on lines 37 to 43
(x.side == y.side && x.G == y.G && x.H == y.H ) || return false
if is_right(x)
# Hx == Hy if x/y in H
return representative(x) / representative(y) in x.H
else
# xH == yH if x\y in H
return representative(x) \ representative(y) in x.H
Copy link
Member

Choose a reason for hiding this comment

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

I find the comment versus object names confusing: $Hx$ corresponds to the Julia variable x; where the $H$ is x.H and the $x$ is representative(x).

Perhaps we can name things a bit and e.g. call the Julia variables differently (say A and B), or the comment variables (e.g. Ha and Hb)

Copy link
Member Author

Choose a reason for hiding this comment

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

o.k.

@fingolfin fingolfin merged commit 0879f92 into oscar-system:master Nov 7, 2024
29 checks passed
@ThomasBreuer ThomasBreuer deleted the TB_cosets_lazy branch November 7, 2024 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants