Jared Parsons
Jared Parsons
> I would assume the assignment of elements with a default value could be omitted. Why would you assume that? The user has explicitly asked the compiler to assign a...
What if the user has disabled locals init behavior and are using the defaults to force initialization?
> could you explain the situation when it can't be optimized out? I've listed a few already in the issue. Which one is unclear? > In my eyes the assignment...
I feel like you haven't fully responded to my last comment 1. What are the very specific cases this would apply to and why is it demonstrably safe in all...
> In my eyes it is obvious that those assignments are unnecessary That is not real data. Data is profiles showing that the optimization actually improves performance. Depending on intuition...
Thansk fro the benchmark. Closing for now because it seems like the runtime is handling these cases fairly good today. Can re-open if we find this is not the case...
@JoeRobich are you able to reprooduce this failure locally? There is not really any info to go off of in the test run that I could see.
> I think it's relevant because today they are in 2 separate projects, while compile include would make them 1 project, and I'm not 100% sure if the compiler is...
This behavior is "By Design". The default for .NET SDK applications is to have deterministic builds. To achieve that the timestamp field is replaced with part of a deterministic hash...
@dangrif have any pointers here?