Why run the min/max of the array #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
on lines 207 and 208 you do
This seems kinda redundant. I threw the api data into a file just to see what it looked like, and the data is already sorted. grabbing the last item of the sell summary and the first of the buy summary would do the same thing but faster right? I'm asking this question not to be snobby, im just curious if there was a reason/something i missed.
No reason that I remember - I assume I just never realised the data was already sorted!
On balance I think I'd rather keep the min/max calculation, just in case. The API documentation doesn't state that the data is ordered, so this provides some protection against future changes, and I don't believe the performance impact is significant.