I was assuming the compiler did not eliminate it. If it does then my point is
moot.
-Mike
Sent from my iPad
> On Apr 26, 2019, at 9:13 AM, Ian Lance Taylor <i...@golang.org> wrote:
>
>> On Thu, Apr 25, 2019 at 10:57 PM Mike Schinkel <m...@newclarity.net> wrote:
>>
>> Marcus Low wrote:
>>>
>>> datalen := removedKeyken // removedKeyken must have been int32 in your
>>> example.
>>> if value != nil {
>>> datalen = len(value)
>>> }
>>
>>
>> The issue with this is it makes two assignments when value != nil instead of
>> just one.
>
> In what sense is that an issue? If you are concerned about
> performance, note that the compiler can eliminate the initial
> assignment in the value == nil case if it is costly.
>
> Ian
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
