Actually those defines were created to allow other files to check for them while keeping the raylib-required types. The problem with this change is that if other files define custom types before raylib, then many raylib internals could broke due to not getting the expected type.

The problem with this change is that if other files define custom types before raylib, then many raylib internals could broke due to not getting the expected type.

Could you please clarify this part? In order for other files to break raylib code, they need to define RL_VECTOR2_TYPE and similar defines. If they do so, they probably know what they do. Current change will only affect code such as

#include "physac.h"
#include "raylib.h"

where includes don't have to be in the specific order. In other cases we assume that no other file is going to define RL_VECTOR2_TYPE which is a good enough assumption since this define is quite unique.

@greenfork I prefer to force the use of raylib defined types and do not allow other previously included files to redefine them (even they know what are they doing), it could suppose a security concern if that is allowed.

Other files using same types could be included after that and use the defines to check for them if required.

@raysan5 alright, thanks for explaining.