4 ms·
> What I was trying to explain is a system that stores the data on the server and passes pointers to this data to the client. What I was trying to explain was
by almkglor 18y ago
> What I was trying to explain is a system that stores the data on the server and passes pointers to this data to the client.
What I was trying to explain was to make this seamless to the programmer, i.e. the programmer doesn't have to use a let-like form listing the variables he or she wants to use, he or she just uses them. Basically the base system scans through the enclosed variables, checks if they're trivial, and encodes them directly if so; if not, it puts the data for retrieval somewhere.
Mostly I'm concentrating on keeping Arc succint, and modifying the base system without, if possible, modifying higher-level code.
In any case your suggested implementation does look good.
> if it is you return the existing id (this can be done efficiently by having two hash tables: ids->values and values->ids).
http://arclanguage.com/item?id=3858 http://arclanguage.com/item?id=3858