New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support destructor-based seq/strings #81

Open

mratsim opened this issue Dec 29, 2019 · 1 comment

Labels

Feature 🚀 memory 💫 upstream 🐉

Owner

mratsim commented Dec 29, 2019

This is more exploratory but being able to return seq string would be a huge boon.

The main unknown is:

do we pass around ownership of a buffer, this requires it to be allocated in shared memory.
or do we copy it in a channel, this restricts the size to Weave max closure size.

Araq commented Dec 30, 2019

The Nim runtime decided for you and uses a shared heap for seqs. ;-)

mratsim added Feature 🚀 memory 💫 upstream 🐉 labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment