Re:About V, the language Volt is written in
by gcb0 on Thursday February 07, 2019 @12:58AM
(#19103358)
You need to stop pretending they are not globals. Just accept you work on one continuous memory patch and are simply passing pointers around. If you don't lie to yourself, you can't shoot your own foot when the compiler do not see your lie.
Re:About V, the language Volt is written in
by nudpiedo on Thursday February 07, 2019 @04:29AM
(#19104076)
not all abstractions are leaky, many compilers/language grammars enforce the paradigm of local lexical contexts.
Playing a game without accept its self imposed restrictions whose player accepted voluntarily would be lying to oneself.
Re:About V, the language Volt is written in
by amedvednikov on Wednesday February 06, 2019 @10:40PM
(#19102814)
Thanks for your input. I'll do more research on this.
> It seems easy to accidentally make allocating code allocate by changing some variable names (b = fnc(a) - oops, allocation)
> I would be extremely wary of trusting a compiler to realize what sort of allocations are optimizable and not - I already have problems with inlining decisions, poor code layout, etc in fairly optimized c++/rust code compiled by gcc+llvm.
Replace allocation with any other expensive work that duplicating a datastructure would result in, and you have the same story. I suspect many of the people that would be evaluating this compared to C/C++/Rust have similar performance concerns.