> I understand why the alternative of changing the generic type parameter list
> symbols was rejected, to be consistent with other C based languages, but I
> don't understand why the following was rejected:
>
> making the UppercaseTypes, lowercaseValues convention a syntactic
> requirement, as is done in ML and Haskell.
> I see that as a good viable alternative.
+1, enforcing the initial character case of type and value identifiers would
clear up the language IMO.
It would also mean we'd need to bridge all C APIs in correct case.
Also, in general +1 to getting rid of `.self`.
— Pyry
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
