[VM/globals] Is there any way to actually avoid them altogether?

[github-actions]

[VM/globals] Is there any way to actually avoid them altogether?

Having all these global variables is practical, but it actually causes problems when we end up wanting to work with multiple threads. An idea would be to add them as fields in a VM object, and pass this object around. But it would still need to be properly benchmark as it would - undoubtedly - add some serious overhead.

arturo/src/vm/globals.nim

Line 21 in ce734e7

# TODO(VM/globals) Is there any way to actually avoid them altogether?

#=======================================

# TODO(VM/globals) Is there any way to actually avoid them altogether?
#  Having all these global variables is practical, but it actually causes problems when we end up wanting to work with multiple threads. An idea would be to add them as fields in a VM object, and pass this object around. But it would still need to be properly benchmark as it would - undoubtedly - add some serious overhead.
#  labels: vm, enhancement, benchmark, open discussion

var
    # symbols
    Syms* {.global.}      : ValueDict
ndex 584dd731a..39eb13156 100644
++ b/src/vm/lib.nim

658ca7972fbf6d3830966a03cc9d6c7d9e3ea816

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

Closing issue as stale.

[drkameleon]

Re-opening as still valid

[stale]

Closing issue as stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

Closing issue as stale.