-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Improve documentation of JoinFeature #34508
Comments
Branch: u/soehms/docu_join_feature_34508 |
New commits:
|
Commit: |
Author: Sebastian Oehms |
Changed branch from u/soehms/docu_join_feature_34508 to u/klee/docu_join_feature_34508 |
comment:5
I made minor edits. In particular, I removed the link to the ticket since the docstring summarizes important points of the discussion in the ticket. (I don't like links to trac tickets in our documentation except obviously necessary cases.) If you are okay, you can set positive-review. New commits:
|
Reviewer: Kwankyu Lee |
comment:7
Replying to Kwankyu Lee:
I don't like them in parts of the reference manual dedicated to end users, either. But here I didn't mind about it.
Anyway, I'm fine with your changes. Thank you! |
comment:8
Replying to Sebastian Oehms:
Exactly. In this case, end users are developers :)
Thanks! |
Changed branch from u/klee/docu_join_feature_34508 to |
As observed in #34282 (see comment 28 ff there) there are two different use cases of this class which need to be explained in the doc-string.
Component: documentation
Keywords: join feature
Author: Sebastian Oehms
Branch/Commit:
68d4fe2
Reviewer: Kwankyu Lee
Issue created by migration from https://trac.sagemath.org/ticket/34508
The text was updated successfully, but these errors were encountered: