Skip to content
This repository was archived by the owner on Oct 19, 2019. It is now read-only.

Questions: cloning, binary size, namespace #47

Open
mchaka opened this issue Dec 31, 2016 · 0 comments
Open

Questions: cloning, binary size, namespace #47

mchaka opened this issue Dec 31, 2016 · 0 comments

Comments

@mchaka
Copy link

mchaka commented Dec 31, 2016

Hello,

I have some questions.

  1. Cloning the worker state (variables)

I dream of doing something like:

  • js: $sendSync(...)
  • go: recvSync(...) {...}
  • clone the state of the worker at the point of the $sendSync was called
  • spin up another worker with the same cloned state
  • work in the clone, mess up everything, get some results
  • return to the original worker
  • have it just like it was.

Could that be made?

  1. Binary size

When I build my tiny project the binary is over 100M. I read that with gcc V8 will be under 10M but I understand my binary has everything linked statically. I'm a total noob with go, haven't really done anything with c++ and don't know where to start. Any info is appreciated.

  1. Namespace

Those $rect, $print etc. are fairly nice but I'd prefer these names customisable, perhaps having them inside an object (foo.print, foo.send, ...). Looking at the code this seems achievable but do you think this is a totally retarded idea?

Anyways, thanks for creating this fine tool. I will have lots of fun with it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant