How to reproduce:
1. Create a new project in your preferred workspace and open it
2. Connect it to Perforce and submit the initial project (Assets/Project settings) (This will be User 1)
3. Get latest with a different user/workspace and open the project (This will be User 2)
4. With User 1 and User 2 create a new material (Make sure the names are the same)
5. With User 1 Submit the material
6. On User 2 observe that the created material is now out of sync
7. On User 2 try to get latest for the material and observe its status

Expected result: a warning is thrown, similar to the P4V one, on why files can't be replaced and if the add state is reverted, files can get overwritten with a confirmation prompt (See notes)
Actual result: nothing happens when trying to get latest, reverting the add state and then trying to get latest on the file throws "Version Control: Can't clobber writable file" error

Reproduced in: 2020.1.0a4, 2019.3.0b3, 2019.2.5f1, 2018.4.8f1, 2017.4.32f1

Notes:
- In P4V an "x is opened for add and can't be replaced" warning is thrown when trying to Get Latest on such files but nothing is thrown in the Editor
- The user has to manually revert the file and even then the Editor does not let the user Get Latest on the file (On P4V a confirmation prompt shows up letting the user replace the writable file)