Re: no function clause matching became no case clause matching exception
Björn Gustavsson <[email protected]>
| Newsgroups | gmane.comp.lang.erlang.general |
|---|---|
| Message-ID | <CA+yh78RN1-yvA0fo8xwvrE1LT_nyaS2nC96JqT7qGi=3dPCDiw@mail.gmail.com> |
On Mon, Dec 13, 2021 at 11:15 AM Mikael Pettersson <[email protected]> wrote: > > I think this is unfortunate. The language specifies different errors > for different > cases, e.g. badmatch, case_clause, function_clause, and I think the error > implied by the original source should be preserved even if the compiler inlines > and rewrites code. If this is not the case there is no reason for the > language to > pretend to have this distinction. > I have written an issue: https://github.com/erlang/otp/issues/5513 We will need a new BEAM instruction to implement this without code bloat, so it can be no earlier than OTP 25. /Björn -- Björn Gustavsson, Erlang/OTP, Ericsson AB