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

Clarify doc of init in map_word #4498

Merged
merged 3 commits into from
Jan 29, 2025

Conversation

TWiedemann
Copy link
Contributor

The behaviour of init has been settled in #3892, but there were some problems with the documentation:

  • The behaviour of init was not documented at all for PcGroups.
  • It was claimed that map_word([], genimgs, init=init) is one(genimgs[1]) if genimgs is non-empty. This is incorrect, it is init.
  • I moved the statement that init is the left-most factor if it is specified to the beginning. I found the way it was done previously confusing.

I also added examples illustrating the behaviour for integer lists and for map_word([], []).

@lgoettgens lgoettgens added documentation Improvements or additions to documentation topic: groups release notes: not needed PRs introducing changes that are wholly irrelevant to the release notes labels Jan 24, 2025
Copy link

codecov bot commented Jan 24, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.55%. Comparing base (f329ec4) to head (12f44b3).
Report is 7 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4498      +/-   ##
==========================================
- Coverage   84.55%   84.55%   -0.01%     
==========================================
  Files         672      672              
  Lines       88888    88833      -55     
==========================================
- Hits        75158    75109      -49     
+ Misses      13730    13724       -6     
Files with missing lines Coverage Δ
src/Groups/GAPGroups.jl 94.11% <ø> (ø)

... and 28 files with indirect coverage changes

Copy link
Member

@ThomasBreuer ThomasBreuer left a comment

Choose a reason for hiding this comment

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

Good. Thanks.


If `init` is different from `nothing`, return $x g_{i_1}^{e_1} g_{i_2}^{e_2} \cdots g_{i_n}^{e_n}$ where $x =$ `init`.

See also: [`map_word(::Union{FPGroupElem, SubFPGroupElem}, ::Vector)`](@ref), [`map_word(::Vector{Union{Int, Pair{Int, Int}}}, ::Vector)`](@ref).
Copy link
Member

Choose a reason for hiding this comment

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

The two references point to the same section. Wouldn't one reference be enough?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right. I removed the second one.

@joschmitt joschmitt merged commit 7f57fbf into oscar-system:master Jan 29, 2025
28 of 31 checks passed
@TWiedemann TWiedemann deleted the tw/map_word_init_doc branch January 29, 2025 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation release notes: not needed PRs introducing changes that are wholly irrelevant to the release notes topic: groups
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants