Raycast function returns what it hit

[MatusGuy]

No description provided.

[pazkero]

LGTM, for what little good it does.

[MatusGuy]

little good??? I need this.

[HybridDog]

If I understand this change correctly, from a user perspective it does nothing. Why do you need this change?

[MatusGuy]

I'm trying to change zeekling's behaviour in order to make it more predictable: #2624
and for that im doing raycasting

[pazkero]

little good??? I need this.

No, I mean my opinion does you little good, you need mrkubax or Vankata or Tobbi or any other C++ coder (up to and including Semphriss, I assume) to this go ahead, the fact I approve is not going to help you.

[MatusGuy]

ah sorry for misunderstanding ur right

[mrkubax10]

Apparently designated initializers (i.e. .tile = tile) are available since C++20.

[MatusGuy]

huh???? ive been doing c++17??? How do i initialize then? Every other way has resulted in compiler error. Any examples?

[mrkubax10]

You are probably using GCC which is much less pedantic about standard than for example Clang or MSVC (though it tends to add it's own weird features lol).

[mrkubax10]

Any examples?

First define the union as not anonymous:

union RaycastHit
{
  const CollisionObject* object;
  const Tile* tile;
};

struct RaycastResult
...

Then use it in struct RaycastResult:

RaycastHit hit;

Initialize it the normal way (for example):

RaycastHit hit;
hit.tile = tile;

And use in return value:

return {true, hit, tilebox};

[MatusGuy]

I see. Do they get initialized as nullptr by default?

[MatusGuy]

You are probably using GCC which is much less pedantic about standard than for example Clang or MSVC (though it tends to add it's own weird features lol).

I believe i was using clang at the time

[mrkubax10]

I see. Do they get initialized as nullptr by default?

Since all union members use the same memory (they are overlapping), only one of them is valid which means that you can't initialize other members.