Eugene Kabanov

This is table of all possible variants. I dont see any reason why 12% should become default. | Protocol | Address | Option | Decision | | -------- | -------...

And this PR do not handle errors properly, so if you want to ignore errors for `::` bind process you should check it for every OS and find what errors...

`NoDualstack` is absolutely redundant. First of all this flags do not have any meaning for IPv4, so there flag should be removed to `IP6DualStack` or something like that, because this...

One more thing is to check at least MacOS for defaults because and i want that documented in this PR too. #### Windows https://docs.microsoft.com/en-us/windows/win32/winsock/ipproto-ipv6-socket-options ``` IPV6_V6ONLY Indicates if a socket...

Yep, its impossible to control `IPV6_ONLY` flag on MacOS and all BSD (including FreeBSD, OpenBSD, NetBSD) and DragonflyBSD which misses `IPV6_V6ONLY` flag at all... #### OpenBSD https://man.openbsd.org/ip6#IPV6_V6ONLY ``` Get or...

Looks like its impossible to achieve acceptable level of cross-platform support for proposed feature.

First of all current dispatcher even if called `global` not actually global for process, it is thread global, so it already thread-safe. What is `undefined init order`? And what is...

One of the biggest problems here is `Future[T]` initialization, to remove dependency on global dispatcher `Future[T]` needs to hold reference to dispatcher, but this will require `{.async.}` procedures to have...

@arnetheduck i understand idea, but i can't figure out how to implement it.

Also you need to consider that usage of more then one dispatcher in one thread is nonsense.