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

Should we define a constructor for the Socket class? #9

Open

Ethan-Arrowood opened this issue Sep 7, 2023 · 1 comment

Contributor

Ethan-Arrowood commented Sep 7, 2023

A constructor for {{Socket}} is intentially not specified, and is left to implementors to create.

Do we want to leave it like this? Are there reasons why implementors might want to create a constructor for Socket? If there are then it's better for us to capture that in this document and avoid every vendor creating their own constructor.

Ethan-Arrowood mentioned this issue

Reorganize Spec for consistency and clarity #8

Merged

Collaborator

jasnell commented Sep 8, 2023

We decided not to so that connect(...) is the only way to create a Socket instance.

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