[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Curious error logic in completion--some

From: Daniel Colascione
Subject: Curious error logic in completion--some
Date: Wed, 26 Feb 2014 14:27:22 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0

Why does completion--some to raise an error only if one of its passed-in functions raises an error and all return nil? If we want to treat an error as "no completions", we should do that consistently or consistently propagate errors to callers. The way it is now, where the interpretation of an error from a completion table depends on what other completion tables are in use, seems odd.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]