You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We have code that abstracts over ets functions, which have ets:type/1 as a parameter type.
Our workaround of having our own type that repeats the definition of ets:type/1 is awkward and not forwards-compatible.
Describe the solution you'd like
Export ets:type/1 or an alias, if a different name is desired
Describe alternatives you've considered
workaround described above
Additional context
In general, when a type is mentioned in exported functions of a module, it makes sense to me to either:
expose the type
if implementation-hiding is necessary, create an opaque wrapper. Expose the opaque wrapper and use the opaque wrapper in specs for exported functions
Is your feature request related to a problem? Please describe.
We have code that abstracts over ets functions, which have
ets:type/1
as a parameter type.Our workaround of having our own type that repeats the definition of
ets:type/1
is awkward and not forwards-compatible.Describe the solution you'd like
Export ets:type/1 or an alias, if a different name is desired
Describe alternatives you've considered
workaround described above
Additional context
In general, when a type is mentioned in exported functions of a module, it makes sense to me to either:
related issues:
The text was updated successfully, but these errors were encountered: