Open kevinresol opened 6 years ago
I don't think this is 4.0 priority, but I'm also not quite sure what this is about.
If I understand correctly, these implementations are actually compatible with sys.ssl.Socket, moving them back to that package saves user from the conditional compilation mess.
Maybe just a typedef is fine.
I agree, but that doesn't sound like it's high priority. Moving to 4.1 for now.
the same problem exists in the csharp target.
The problem is: C# doesn't have a SslSocket implementation: https://github.com/HaxeFoundation/haxe/issues/7543
They currently sits in:
python.net.SslSocket
php.net.SslSocket
java.net.SslSocket