|
From: | Wanrong Lin |
Subject: | bug#39484: 26.3; try-completion bug |
Date: | Wed, 28 Oct 2020 08:59:24 -0400 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 |
So in summary, my two points:1. Return value is not ideal. You can argue it is still not wrong, but I think we can improve. 2. Even if we don't change anything here, we need to make this less-than-ideal behavior clear in the documentation (doc string).
I hope I convinced at least some of you. Wanrong On 10/28/2020 7:44 AM, Andreas Schwab wrote:
On Okt 28 2020, Lars Ingebrigtsen wrote:Andreas Schwab <schwab@linux-m68k.org> writes:The case always matches one of the candidates.Yes. An arbitrary candidate (well, the first one, but it's not documented, which means that it's arbitrary).It is not nessesary to document each and every implementation detail. That makes it difficult to change the implementation later, and it also unduly restricts the way a collection function can handle that situation. Andreas.
[Prev in Thread] | Current Thread | [Next in Thread] |