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
The difference between strings and symbols can be confusing, because there are special symbols, #authority and #ambient, and normal symbols that can be user defined. Those are just be considered as special strings with limited constraints checks, and a bit faster to compare since they're actually stored as an index in the symbols table.
I'd propose that we store all strings in the symbol tables (this can reduce storage size as strings tend to be repeated) and reserve the symbol type to reserved symbols (only #authority and #ambient for now).
This would require that the Datalog engine accesses the symbol table during execution (for string constraints checks)
The text was updated successfully, but these errors were encountered:
it might make he format a lot more complex though. Symbol tables already come with a high complexity budget, since they must support adding strings at each new block
The difference between strings and symbols can be confusing, because there are special symbols,
#authority
and#ambient
, and normal symbols that can be user defined. Those are just be considered as special strings with limited constraints checks, and a bit faster to compare since they're actually stored as an index in the symbols table.I'd propose that we store all strings in the symbol tables (this can reduce storage size as strings tend to be repeated) and reserve the symbol type to reserved symbols (only
#authority
and#ambient
for now).This would require that the Datalog engine accesses the symbol table during execution (for string constraints checks)
The text was updated successfully, but these errors were encountered: