We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version Used: dotnet 6.0.308
Steps to Reproduce:
It happens if pointers is used
long x = 10; unsafe { Console.WriteLine(*&x); } await Task.Delay(1000); unsafe { Console.WriteLine(*&x); }
Expected Behavior: prints 10 both times
Actual Behavior: prints 10 and 0
The text was updated successfully, but these errors were encountered:
If I assign same variable it works as expected
long x = 10; unsafe { Console.WriteLine(*&x); } await Task.Delay(1000); x = x; unsafe { Console.WriteLine(*&x); }
Sorry, something went wrong.
I suspect that we're not treating & as read operations in our lifting logic here and that is what causes this issue.
&
&local
async
jcouv
Successfully merging a pull request may close this issue.
Version Used: dotnet 6.0.308
Steps to Reproduce:
It happens if pointers is used
Expected Behavior: prints 10 both times
Actual Behavior: prints 10 and 0
The text was updated successfully, but these errors were encountered: