Is ETS table of type ordered_set able to do efficient range search with match spec?

[sverker]

ETS is not smart enough to utilize guards like Timestamp > Time1 to limit the search space. It will only utilize fully bound keys and partially bound keys in the head of the match spec as described at the bottom of this section:
https://www.erlang.org/doc/man/ets.html#table-traversal

See also this recent forum thread:

Variable shadowing constraint of match spec generated using ms_transform

Looks like that is a variable shadowing constraint of match spec that is generated using ms_transform. For example, get_match_spec(Id) -> ets:fun2ms(fun({Id, Content} = Item) -> {Id, [mark | Content]} end). Warning: variable 'Id' shadowed in ms_transform fun head get_match_spec(123). Output: [{{'$1','$2'},[],[{{'$1',[mark|'$2']}}]}] Thus ets:select_replace can’t efficiently be used to select_replace an item with the given Id. One way is to use guard get_match_spec(Id) -> ets:fun2ms(…