diff options
| author | Björn Gustavsson <[email protected]> | 2013-01-28 15:41:18 +0100 |
|---|---|---|
| committer | Björn Gustavsson <[email protected]> | 2013-01-31 11:14:47 +0100 |
| commit | e5d592e8258095a49d112fafeb5d67e85d196727 (patch) | |
| tree | b0d86465785f7d5681fee212b6ce0daf1230ecff /lib/stdlib/test/ets_SUITE_data | |
| parent | e26788bf716eab7dfbfc6a1ea000b5d428a99c40 (diff) | |
| download | otp-e5d592e8258095a49d112fafeb5d67e85d196727.tar.gz otp-e5d592e8258095a49d112fafeb5d67e85d196727.tar.bz2 otp-e5d592e8258095a49d112fafeb5d67e85d196727.zip | |
Remove error handling for calling a BIF that is not auto-imported
All guards BIFs are auto-imported. That can be verified like this:
[] = [{F,A} || {erlang,F,A} <- erlang:system_info(snifs),
erl_internal:guard_bif(F, A),
not erl_internal:bif(F, A)]
Therefore, calling a guard BIF in a guard without a module name
is always allowed (provided that there is not a local function or
an import with the same name), and therefore we can remove the
error reporting code. But keep an assertion so that we will find
out if any non-auto-imported guard BIFs are added in the future.
Diffstat (limited to 'lib/stdlib/test/ets_SUITE_data')
0 files changed, 0 insertions, 0 deletions