#13875: Test memory allocation in distances_all_pairs
---------------------------------+------------------------------------------
Reporter: dcoudert | Owner: jason, ncohen, rlm
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.6
Component: graph theory | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: David Coudert | Merged in:
Dependencies: | Stopgaps:
---------------------------------+------------------------------------------
Comment (by ncohen):
Yoooooooooo !!
Well, the point of not having #13808 depend on this very patch is that
#13808 is complicated enough *AND* already reviewed. And what's the point
of testing whether the pointers are not null when the function cannot
return NULL pointers ? It is checked, the function just can't return NULL
pointers `O_o` The cost is negligible but what's the point as what it does
is useless ? The code is not that easy to read, so let's remove the
maximum amount of useless stuff ! And if we happen to copy/paste code from
this file to another one, we won't copy useless checks at the same time !
`O_o`
Nathann
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13875#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
