2 ms·
> they only just got it working at all WSLg was launched over a year ago > I think the last couple comments on your example link make it clear that this featu
by NavinF 4y ago
> they only just got it working at all
WSLg was launched over a year ago
> I think the last couple comments on your example link make it clear that this feature doesn't really exist on WSL1 or WSL2
They made it clear that this syscall will not be implemented at all in WSL1. With WSL2 on the other hand, they are willing. That’s what a feature freeze looks like.
- Dylan16807 4y agoSaying to make a new ticket isn't exactly saying they're willing, though. The "fixed in wsl2" tag would be more damning but it's not on many newer issues and looking at a few it didn't seem like it was generally used as a resolution, I think? I found one issue directly saying they weren't dismissing it because they're done with WSL1 but because it's a minor TCP difference that the code should be less fragile about.