Re: no function clause matching became no case clause matching exception
Roger Lipscombe <[email protected]>
| Newsgroups | gmane.comp.lang.erlang.general |
|---|---|
| Message-ID | <CAJgnQd-E4Ag3U4xaV+McTuavpFuEUVgWv+JApCkbpNMvarnRng@mail.gmail.com> |
On Fri, 10 Dec 2021 at 14:52, Frans Schneider <[email protected]> wrote: > The following list comprehension used to give a no function clause > matching exception in previous version of Erlang. Now it will emit a no > case clause matching exception. Is this expected behavior? Which versions? I've tested on OTP-24.1.7, and it gives me a function clause error: Erlang/OTP 24 [erts-12.1.5] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [jit] Eshell V12.1.5 (abort with ^G) 1> [(fun(a) -> "a" end)(R) || R <- [a, b, c]]. ** exception error: no function clause matching erl_eval:'-inside-an-interpreted-fun-'(b)