[felipensp]

Fix #23582

[huly-for-github]

Connected to Huly®: V_0.6-22014

[JalonSolov]

Really? unsafe is supposed to be an escape hatch to do whatever you need to do. As I said in the issue, if you use it unwisely, that is your own fault, not V's.

[felipensp]

Really? unsafe is supposed to be an escape hatch to do whatever you need to do. As I said in the issue, if you use it unwisely, that is your own fault, not V's.

So call it const is pretty inconsistent. It should be mut.

[JalonSolov]

No, it is completely const unless you "color outside the lines" by using unsafe.

Using unsafe is telling the compiler "Yes, I know this is bad, but it is something I really need to do, so stop complaining about it."

[JalonSolov]

@medvednikov What do you think?

[medvednikov]

I agree with the PR. It's too much power, even for unsafe.

[medvednikov]

Can be changed to a __global if it's absolutely necessary.

[jorgeluismireles]

Can be changed to a __global if it's absolutely necessary.

Or building with preference -translated as I see in the commit.

[felipensp]

Can be changed to a __global if it's absolutely necessary.

Or building with preference -translated as I see in the commit.

Yes. -translated builds are not affected. 👍🏻