Cool. Thanks for figuring it out and posting your answer.
On Tuesday, 15 November 2016 07:28:16 UTC+11, Evan Digby wrote:
>
> Confirmed bug on my part.
>
> When using the "..." suffix to pass a slice into a func with variadic args
> it passes through the the original slice, rather than
Confirmed bug on my part.
When using the "..." suffix to pass a slice into a func with variadic args
it passes through the the original slice, rather than constructing a new
one. An obvious optimization, but caused my function to act differently in
my tests vs. a real use case.
The tests
I think I've eyeballed a bug in my code that *might* cause this but I won't be
at a computer for a day or two to verify. I'll keep here posted!
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving
On a second glance, there's no real IP here. Let's not complicate things--I
just ask that nobody judge the state of this code, unless that state is the
reason for the strange benchmark results!
This won't run in playground since it's a benchmark, but provided as a
nicer place to paste:
Can you post a runable sample so that other can try to reproduce your issue?
On Friday, 11 November 2016 12:06:21 UTC+11, Evan Digby wrote:
>
> Is it expected that if multiple sub-benchmarks are run in the same
> benchmark, the cost of the setup will impact the results from the first
>
