> Assuming Result can only ever be OK or Err, this is basically an Either type Yes. It is the same concept. SRP is rather vague, and interpreted differently d

> Assuming Result can only ever be OK or Err, this is basically an Either type Yes. It is the same concept. SRP is rather vague, and interpreted differently depending on when and where to apply it (SRP for microservices is very different from SRP for a method). But for the Either, or the Result, it applies perfectly. Because this thing does only one thing: it discrimates between this or that: it leaves what this and that do, are, mean etc to this and to that. I was trying to put forward examples where the code does both this discrimination and applies the resulting meaning from it. In dynamically typed languages a bigger problem than in many others, where e.g. "null" or "some object of type X" or "a string with the error message" are far too common as return values.