Join GitHub today
[RFC] Implement setsockopt and getsockopt support #2104
Setting socket options isn't currently possible unless the user's using IO::Socket::INET and a recent version of MoarVM, and requires using NativeCall. This makes for a lot of boilerplate in projects that need to be able to access socket options.
To get the options, an op like
The problem with this is how should errors be handled? i don't think it'd be a good idea to ignore them like the way I've written this does. Better yet, is it a good idea to have in the language at all for v6.d?