The expected behavior is that there should be confusion with which pronoun is to be used. But the template is created with the assumption that the first pronoun is used. This may be okay, but unsatisfactory and can lead to silent bugs downstream.
Maybe one way to get around this is to allow for types to be specified using fully qualified names like:
The following test fails
The expected behavior is that there should be confusion with which
pronoun
is to be used. But the template is created with the assumption that the first pronoun is used. This may be okay, but unsatisfactory and can lead to silent bugs downstream.Maybe one way to get around this is to allow for types to be specified using fully qualified names like:
This will remove all ambiguity about which pronoun we are talking about.