<source>All branches of a pattern match expression must return values of the same type as the first branch, which here is '{0}'. This branch returns a value of type '{1}'.</source>
<source>All branches of a pattern match expression must return values of the same type as the first branch, which here is '{0}'. This branch returns a value of type '{1}'.</source>
<target state="translated">Todas las ramas de una expresión de coincidencia de patrón deben devolver valores del mismo tipo. La primera rama devolvió un valor de tipo "{0}", pero esta rama devolvió un valor de tipo "\{1 \}".</target>
<target state="new">All branches of a pattern match expression must return values of the same type as the first branch, which here is '{0}'. This branch returns a value of type '{1}'.</target>
<source>A default implementation of this interface has already been added because the explicit implementation of the interface was not specified at the definition of the type</source>
<targetstate="new">A default implementation of this interface has already been added because the explicit implementation of the interface was not specified at the definition of the type</target>
<source>Recursive bindings that include member specifications can only occur as a direct augmentation of a type</source>
<targetstate="new">Recursive bindings that include member specifications can only occur as a direct augmentation of a type</target>
<note/>
</trans-unit>
<trans-unitid="tcRequireMergeSourcesOrBindN">
<trans-unitid="tcRequireMergeSourcesOrBindN">
<source>The 'let! ... and! ...' construct may only be used if the computation expression builder defines either a '{0}' method or appropriate 'MergeSource' and 'Bind' methods</source>
<source>The 'let! ... and! ...' construct may only be used if the computation expression builder defines either a '{0}' method or appropriate 'MergeSource' and 'Bind' methods</source>
<source>The implicit instantiation of a generic construct at or near this point could not be resolved because it could resolve to multiple unrelated types, e.g. '{0}' and '{1}'. Consider using type annotations to resolve the ambiguity</source>
<source>The implicit instantiation of a generic construct at or near this point could not be resolved because it could resolve to multiple unrelated types, e.g. '{0}' and '{1}'. Consider using type annotations to resolve the ambiguity</source>