API behavior congruity

Question

API behavior congruity

Closed this issue 9 years ago · 3 comments

The rest of gonum has the property that if a destination slice is nil, a new slice is allocated. floats does not follow this property. Should it?

If so, these are the ones that need it:
AddScaledTo
AddTo
CumProd
CumSum
DivTo
MulTo
SubTo

Answer 1 · 2016-03-15T15:51:53.000Z

For reference, the primary reason floats does not match the API is that the current floats behavior is older than the establishment of the convention. The reason to keep the current behavior is that it forces users to think about efficiency when interacting with floats (users must see their allocations).

Answer 2 · 2016-03-15T21:45:00.000Z

I think that given the primitives nature of floats it makes sense to not do too much. I think it's fine as it is.

Answer 3 · 2016-03-15T21:45:51.000Z

Okay, that's reasonable. Wanted to mention before 1.0.