17390, "mppf", "CG: how to handle return intent overloading?", "2021-03-10T21:39:40Z"
main issue: #8629 abstract intents: spec
When return intent overloading is used, a function call will resolve to a different function depending on how the result is used (in particular - if it is set or not). How will constrained generics interact with this feature? Do constrained generic interfaces need to indicate that return intent overloading is a possibility if the CG functions can use it? Is it possible for something to implement an interface if only (say) the
ref return version is provided?
There are probably other questions related to this combination of features.