Skip to content

Rationale behind not setting positional arguments to positional only for few functions. #475

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.

Sign up for GitHub

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

Jump to bottom
Closed
RickSanchezStoic opened this issue Sep 7, 2022 · 3 comments · Fixed by #730
Closed

Rationale behind not setting positional arguments to positional only for few functions. #475

RickSanchezStoic opened this issue Sep 7, 2022 · 3 comments · Fixed by #730
Labels
Narrative Content Narrative documentation content. Question General question.

Comments

@RickSanchezStoic
Copy link

Functions like full and ones and maybe others don't have positional only arguments in their definition. I wanted to know the reason behind this. https://data-apis.org/array-api/latest/API_specification/creation_functions.html?highlight=positional
@kgryte
Copy link
Contributor

kgryte commented Sep 7, 2022

This was changed in #167 and stemmed from the following issue: #85.

@RickSanchezStoic
Copy link
Author

Thanks, @kgryte! Do you think there should be some detail about this in the official documentation to avoid confusion in the future?

@kgryte
Copy link
Contributor

kgryte commented Sep 8, 2022

Agreed. We have an open issue to consolidate some of the spec guidance (see #223), and, as part of addressing the concerns described there, can add an explainer regarding exceptions to the general rule.

@kgryte kgryte added Question General question. Narrative Content Narrative documentation content. labels Sep 8, 2022
@kgryte kgryte mentioned this issue Jun 29, 2023
Closed
17 tasks
rgommers added a commit to rgommers/array-api that referenced this issue Jan 11, 2024
@rgommers
A few updates to the "function and method signatures" section
0bd4ab6 
The type annotations part was a little outdated. For the positional
and keyword-only descriptions, improve the language to account for
exceptions to the default design rules.

Closes data-apisgh-475
@rgommers rgommers mentioned this issue Jan 11, 2024
Merged
rgommers added a commit to rgommers/array-api that referenced this issue Jan 12, 2024
@rgommers
A few updates to the "function and method signatures" section
0fe08ae 
The type annotations part was a little outdated. For the positional
and keyword-only descriptions, improve the language to account for
exceptions to the default design rules.

Closes data-apisgh-475
kgryte pushed a commit that referenced this issue Jan 22, 2024
@rgommers
Clarify guidance in the "function and method signatures" section
0cde841 
The type annotations part was a little outdated. For the positional
and keyword-only descriptions, improve the language to account for
exceptions to the default design rules.

Closes: #475
PR-URL: 	#730
Reviewed-by: Athan Reines <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Narrative Content Narrative documentation content. Question General question.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

A few updates to the "function and method signatures" section rgommers/array-api
2 participants
@kgryte @RickSanchezStoic