Re: The effect of ref
Adam D. Ruppe wrote: On Friday, 22 November 2019 at 03:42:26 UTC, dokutoku wrote: Is there a difference in the execution speed and stability when executing the program by rewriting the parameter of the function argument like this? the generated code the processor sees is generally identical, but the `ref` version is potentially better because then X cannot possibly be `null` which can help you write better code and might help the optimizer too. still, using explicit pointers may be good for readability. int a; foo(a); // does it chage `a`? boo(); // oh, yeah, now i see that it will prolly change `a` unsafe coding style, but for me pointers for `ref` are more readable.
Re: The effect of ref
On Friday, 22 November 2019 at 03:42:26 UTC, dokutoku wrote: Is there a difference in the execution speed and stability when executing the program by rewriting the parameter of the function argument like this? the generated code the processor sees is generally identical, but the `ref` version is potentially better because then X cannot possibly be `null` which can help you write better code and might help the optimizer too.
Re: The effect of ref
On Friday, 22 November 2019 at 03:42:26 UTC, dokutoku wrote:
Is there a difference in the execution speed and stability when
executing the program by rewriting the parameter of the
function argument like this?
```d
void test1 (int * X)
{
// some processing
}
void test2 (ref int X)
{
// some processing
}
```
The Compiler Explorer supports D, so it's a good way to
ask these questions.
https://godbolt.org/z/gnR6Eu
int example.test1(int*):
mov eax, DWORD PTR [rdi]
imuleax, eax
add eax, 1
ret
int example.test2(ref int):
mov eax, DWORD PTR [rdi]
imuleax, eax
add eax, 1
ret
The effect of ref
Is there a difference in the execution speed and stability when
executing the program by rewriting the parameter of the function
argument like this?
```d
void test1 (int * X)
{
// some processing
}
void test2 (ref int X)
{
// some processing
}
```
