Agreed for ML. However, F# is not exactly ML. It lives on top of, and has to interoperate with, the existing .NET ecosystem.
That means, for example, that a lot of the datatypes you'll end up dealing with are object-oriented. Those can be difficult to work with in a generic way without resorting to reflection.
That means, for example, that a lot of the datatypes you'll end up dealing with are object-oriented. Those can be difficult to work with in a generic way without resorting to reflection.