{"action":"created","issue":{"url":"https://api.github.com/repos/rustbridge/neon/issues/55","repository_url":"https://api.github.com/repos/rustbridge/neon","labels_url":"https://api.github.com/repos/rustbridge/neon/issues/55/labels{/name}","comments_url":"https://api.github.com/repos/rustbridge/neon/issues/55/comments","events_url":"https://api.github.com/repos/rustbridge/neon/issues/55/events","html_url":"https://github.com/rustbridge/neon/issues/55","id":131910353,"number":55,"title":"Question: does Neon used Shared or Copy memory interfacing","user":{"login":"jadbox","id":595843,"avatar_url":"https://avatars.githubusercontent.com/u/595843?v=3","gravatar_id":"","url":"https://api.github.com/users/jadbox","html_url":"https://github.com/jadbox","followers_url":"https://api.github.com/users/jadbox/followers","following_url":"https://api.github.com/users/jadbox/following{/other_user}","gists_url":"https://api.github.com/users/jadbox/gists{/gist_id}","starred_url":"https://api.github.com/users/jadbox/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jadbox/subscriptions","organizations_url":"https://api.github.com/users/jadbox/orgs","repos_url":"https://api.github.com/users/jadbox/repos","events_url":"https://api.github.com/users/jadbox/events{/privacy}","received_events_url":"https://api.github.com/users/jadbox/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-06T23:17:33Z","updated_at":"2016-02-08T18:56:54Z","closed_at":"2016-02-08T18:56:54Z","body":"For receiving and sending data from V8 through function invocation, are the parameters copied as well as the return object? I across the below article and thought it might be interesting if Neon support shared memory IO into V8.\r\n\r\nhttp://blog.scottfrees.com/how-not-to-access-node-js-from-c-worker-threads"},"comment":{"url":"https://api.github.com/repos/rustbridge/neon/issues/comments/181519587","html_url":"https://github.com/rustbridge/neon/issues/55#issuecomment-181519587","issue_url":"https://api.github.com/repos/rustbridge/neon/issues/55","id":181519587,"user":{"login":"dherman","id":307871,"avatar_url":"https://avatars.githubusercontent.com/u/307871?v=3","gravatar_id":"","url":"https://api.github.com/users/dherman","html_url":"https://github.com/dherman","followers_url":"https://api.github.com/users/dherman/followers","following_url":"https://api.github.com/users/dherman/following{/other_user}","gists_url":"https://api.github.com/users/dherman/gists{/gist_id}","starred_url":"https://api.github.com/users/dherman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dherman/subscriptions","organizations_url":"https://api.github.com/users/dherman/orgs","repos_url":"https://api.github.com/users/dherman/repos","events_url":"https://api.github.com/users/dherman/events{/privacy}","received_events_url":"https://api.github.com/users/dherman/received_events","type":"User","site_admin":false},"created_at":"2016-02-08T18:56:54Z","updated_at":"2016-02-08T18:56:54Z","body":"At least for now, the kinds of patterns of parallelism you can use are limited, because the goal is to retain Rust's memory and concurrency safety guarantees, in particular freedom from data races. I have doubts we'd be able to support shared memory IO but I'd certainly be open to learning safe ways of making that work."}}