-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
Documentation: Explain that min, max do not work for SR #29802
Comments
comment:1
This is Python's built-in min. Try |
comment:2
@mkoeppe, thanks, sorry for the noise, I searched pretty hard for this information (using Google and trac search). I wonder how we could make this information more discoverable? Perhaps adding a |
comment:4
I am pretty sure we tried doing something along the lines of making this easier to find, but apparently not. For instance, it could be useful in plot documentation too - see here. See also: As for the suggestion, are there any other builtins that we are able to treat in this manner? Other than things like |
comment:5
Interestingly, we actually do do this for
But presumably we want something more than that, such as the content here. I'm not sure why this is what is returned. Anyway - maybe that means we can overload |
comment:6
See also #24296 |
comment:8
Setting new milestone based on a cursory review of ticket status, priority, and last modification date. |
On 9.2beta0
returning a in both cases would be best, but at the very worst this should consistently throw an error imo.
Component: documentation
Keywords: symbolics, infinity, minimum, maximum
Issue created by migration from https://trac.sagemath.org/ticket/29802
The text was updated successfully, but these errors were encountered: