"alias_on" seems like an early optimization for nodes that are currently links to other nodes.
The concept could be ok: if coupled for example for the RAWSTRING type and implement faster pointers that shortcut
address resolution.
The problem is that I'm not sure that it works this way. It seems to be used only in GetVal/SetVal functions, so it is probably very incomplete. I would recommend its removal - before, maybe, rewrite it as an cache for the RAWSTRING based address resolution.
"alias_on" seems like an early optimization for nodes that are currently links to other nodes.
The concept could be ok: if coupled for example for the RAWSTRING type and implement faster pointers that shortcut address resolution.
The problem is that I'm not sure that it works this way. It seems to be used only in GetVal/SetVal functions, so it is probably very incomplete. I would recommend its removal - before, maybe, rewrite it as an cache for the RAWSTRING based address resolution.