[WIP] feat: net.Socket

[ebebbington]

Partially addresses #666

Moved from https://github.com/denoland/deno, see here for original PR

• Tests
• All code required copied over
• Port bindings
• Port requires
• Port primordials
• Port JS to TS (largely relies on bindings)

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Edward Bebbington seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[ebebbington]

Regarding the latest comments in the original PR, myself and @bartlomieju discussed a few bits on discord:

[ebebbington]

@bartlomieju How would i go about "emulating" some of the internal bindings? Is it just a matter of finding the source code and converting it from c++ into typescript?

[bartlomieju]

@bartlomieju How would i go about "emulating" some of the internal bindings? Is it just a matter of finding the source code and converting it from c++ into typescript?

@ebebbington yes, pretty much

[ebebbington]

I believe there's only 1 require statement i need to address, and the rest is porting bindings and adding types

[ebebbington]

Stopping work on this PR for the time being, until either bindings are implemented (im unable to do them unfortunately) or when #695 is merged (then ill get the tests sorted)

[jopemachine]

@bartlomieju How would i go about "emulating" some of the internal bindings? Is it just a matter of finding the source code and converting it from c++ into typescript?

@ebebbington yes, pretty much

As far as I know, Deno uses tokio instead of libuv to handle Async I/O.

Is it possible to emulate these internal bindings (c++ code like tcp_wrap.cc) without libuv?

Should it be implemented through tokio?

[ry]

@ebebbington Thanks for the work on this patch - I'm going to close it tho because it's stale and not close to being mergeable. We very much would like to support std/node/net so hopefully we can come back and reference this patch when someone attempts to undertake it.

[ebebbington]

@ebebbington Thanks for the work on this patch - I'm going to close it tho because it's stale and not close to being mergeable. We very much would like to support std/node/net so hopefully we can come back and reference this patch when someone attempts to undertake it.

Fair enough :) unfortunately I probably won’t have enough time in the future to carry on with it so best of luck to whoever may wish to take it on in the future!