I have 2 Interpretations of this Issue :
[ Interpretation A ] Prime-facie : It is unnecessary to state "Same type" , which is redundant & already agreed with , by convention.
It looks like "Over-Sight" by Tao.
Page 284 A.7 Equality :
Tao says that Equality is a relation linking 2 Objects of Same type.
Page 285 A.7 Equality :
Tao says that Set & Number should not be compared using/with/via Equality.
Like-wise , Number & Vector should not be compared using/with/via Equality.
More-over , the Convention is that when we use Equality on Different types , it is automatically false.
Tao says that it is "abuse of notation" to compare 2 Classes or 2 types : Eg $1=1/1$ & $1=1.0$ , though it is generally ok.
That is not a justification to make the Axiom use "Same type" , because , even with "abuse of notation" , we can still conclude that Eg $1/1=1$ & $1.0=1$ , giving Symmetry.
In other words , Symmetry Axiom using "Same type" is unnecessary & redundant : It is still true without that wording.
[ Interpretation B ] Basically : Symmetry Axiom is not concerned or bothered when we have 2 Classes or types. Symmetry Axiom makes no claim in that Scenario. It is outside the Scope of the Symmetry Axiom.
There is a Deeper Issue which Tao is not Explicitly mentioning. This is my thought , I am not claiming that Tao is agreeing with this. I get this interpretation when reading between the lines.
When using 2 Classes or types , all bets are off !
It may be Symmetric ; It may be Anti-Symmetric ; It may be something else !
Page 284 A.7 Equality :
Tao says : Depending on the Class or type , Equality Definition is made to suit that Case & It is arbitrary.
Equality Definition is generally not made on 2 Classes or 2 types.
When we have 2 Classes or 2 types , the Definition may or may not satisfy Symmetry : It is outside the Scope of the Symmetry Axiom.
[ Example 1 ] In Numerical Software terms , we may compare Integers & floating Point Numbers :
"1==1.0" may convert Integer "1" to floating Point "1.000000021" & then the comparison is not true.
"1.0==1" may convert floating Point "1.0" to Integer "1" & then the comparison is true.
No Symmetry.
[[ this is entirely Possible in Certain CPU Architectures ]]
Symmetry Axiom has nothing to say about that Case.
[ Example 2 ] Definition of $=$ on Individual Cases is arbitrary. Consider my new Definition of $=$ to mean "inclusion" or "is" :
Then "Socrates is (=) A human" is true , while "A human is (=) Socrates" is not true.
No Symmetry.
[[ this is entirely Possible in unorthodox theories ]]
Symmetry Axiom has nothing to say about that Case.
[ Example 3 ] Consider a fictitious Example.
Let "X" be some human & "the President" be the Post , where have 2 Classes or 2 types.
Thus , "X is (=) the President" may or may not be true while "The President is (=) X" may be always not true.
No Symmetry.
[[ this is entirely Possible in Object Oriented Programming ]]
Symmetry Axiom has nothing to say about that Case.
With that Interpretation : It is necessary to give the Criteria that we have "Same type" in Symmetry Axiom to exclude the Other Cases : Axiom makes no claim about the Other Cases.