I noticed that using the == operator using the FString types returns true even if the strings are different in case (e.g. CaKe == cAKe returns true) This is different behaviour than normal string comparisons. Is this expected?
That’s how Epic decided to implement operator== for FString. It just calls
Lhs.Equals(Rhs, ESearchCase::IgnoreCase) which I find unintuitive 
.
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.