Hi all, On Wed, May 31, 2023 at 10:02:45AM +0200, Tim Düsterhus wrote: > Aurelien, > > On 5/31/23 09:57, Aurelien DARRAGON wrote: > > would not fit properly with existing representation for converters > > within the doc > > > > > iif(str,str): str <= bool > > > > and > > > > > iif(str,str): bool => str > > > > could be good candidates (fetches are already represented using > > "name(arg) : out"), although dconv would have to be patched anyway for > > If fetches already have the output type after the colon, then the converter > should not have the input type after the colon, i.e. > > iif(str,str): bool => str > > is confusing, because it looks like it returns a bool, ... I guess? > > iif(str,str): str <= bool > > is better, because the colon is followed by the output type, but the order > of "reading" is a little funky with the actual input on the very right side. > > Another option might be listing the "implicit" parameter as a real > parameter: > > iif(bool,str,str): str
Alright, at least it means we have something non-trivial to improve here, so better not change it for 2.8 so that we have plenty of time to rethink all this (including the way we present them in the doc) past the release. Thank you, that's exactly what I needed ;-) Willy
