SocketWrapper | protocol oriented wrapper around the POSIX socket API | Networking library

From this doc: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import

The name parameter is the name of the "module object" which will be used as a kind of namespace to refer to the exports. The export parameters specify individual named exports, while the import * as name syntax imports all of them.

That means if you use import * as io from 'socket.io-client', the io is a kind of namespace.

In your mock file, the io is an object and export default io;

If you use import * as io from 'socket.io-client'. The value of io variable will be:

As Patrick Hofman already answered, you're missing a reference to System.Net.Sockets.

You can use the Visual Studio Package Manager to get it from NuGet.

The window can be accessed over the menu with VIEW > Other Windows > Package Manager Console

In the console, you have to simple write your requested package.

So in your case write Install-Package System.Net.Sockets.

No.

You're on the right lines, but actually you can't call any container member function from different threads at the same time and expect it to work reliably, because the implementation of those member functions themselves are not [guaranteed to be] thread-safe.

I don't see why it would be a problem

Off the record, I'd agree that in the particular case of std::list I wouldn't expect much in the way of practical problems here. Some shops may consider this sufficient reason to go ahead and use this in production. I wouldn't accept it at code review though. The point is that we simply can't* know exactly what the innards do.

That being said, if you have some special stdlib implementation (or a stdlib implementation with a special flag/switch/option) that does provide this guarantee, then knock yourself out ;) * And at the end of the day you could inspect its code and make that determination for yourself, but honestly that way madness lies!

deinit is not called on instances that have not been correctly initialized.

If init fails for some reason, then the class instance never starts existing. Therefore, there is no instance on which deinit could be called.

If deinit could be called on a partially initialized instance, it would break the contract of non-optional properties - in your example the socket property would not get assigned and it would still be accessible in deinit as a non-optional but without a value.