Rig*_*leg 3 erlang reference elixir ets
我正在使用Elixir 1.6.3.我正在使用:etsElixir中的Erlang 模块,我对:ets.new/2函数的返回值感到有点困惑.
根据doc的例子,在调用时:ets.new(:whatever, []),我应该返回一个看似是整数值的东西:
iex> table = :ets.new(:buckets_registry, [:set, :protected])
8207
Run Code Online (Sandbox Code Playgroud)
但是,当我运行完全相同的代码时iex,我得到一个引用:
iex(1)> table = :ets.new(:buckets_registry, [:set, :protected])
#Reference<0.1885502827.460455937.234656>
Run Code Online (Sandbox Code Playgroud)
那么,自编写文档以来有什么变化吗?或者它是一样的,我对参考是什么感到困惑?
是的,ets:new在Erlang/OTP 20.0中,返回值从整数更改为引用.来自README:
OTP-14094 Application(s): stdlib
*** POTENTIAL INCOMPATIBILITY ***
Optimized ETS operations by changing table identifier
type from integer to reference. The reference enables a
more direct mapping to the table with less potential
lock contention and makes especially creation and
deletion of tables scale much better.
The change of the opaque type for the ETS table
identifiers may cause failure in code that make faulty
assumptions about this opaque type.
The number of tables stored at one Erlang node *used*
to be limited. This is no longer the case (except by
memory usage). The previous default limit was about
1400 tables and could be increased by setting the
environment variable ERL_MAX_ETS_TABLES before starting
the Erlang runtime system. This hard limit has been
removed, but it is currently useful to set the
ERL_MAX_ETS_TABLES anyway. It should be set to an
approximate of the maximum amount of tables used. This
since an internal table for named tables is sized using
this value. If large amounts of named tables are used
and ERL_MAX_ETS_TABLES hasn't been increased, the
performance of named table lookup will degrade.
Run Code Online (Sandbox Code Playgroud)