Has this been tested with enum structs?

Any thoughts on how this does/should behave when dataSize/size is not equal to 4 and a float array is passed?

Has this been tested with enum structs?

They don't have a stable in-memory representation so I don't think it really matters, but there shouldn't be any technical problems with these and them.

Any thoughts on how this does/should behave when dataSize/size is not equal to 4 and a float array is passed?

In that case, yea, it would make sense to have a separate func for floats like GetEntDataArrayFloat that doesn't allow the data size to be changed.

I guess this PR depends on the trajectory and philosophy of SP. Personally, I want to give plugin authors all the power. Want to pass an enum struct or float array and do some weird magic with the data size? Go ahead.

@asherkin I think this is cool. The natives are already pretty unsupported ({G,S}etEntData in the sense that they're completely unsafe - opening this up to what was intended (arbitrary sizes) will likely make things more clear.

With this being said, if we macro'd this that would be the way to make it more robust.