Re:Zero-Cost POSIX Compliance: Encoding the Socket State Mac...
by tczMUFlmoNk on Tuesday March 24, 2026 @10:59PM
(#47512705)
This is what I was thinking, too. Without some kind of linearity, `connect` et al. don't give the claimed guarantees if you can just reuse the old socket handle. Especially if it's aliased in a list or something. I was surprised to see this not mentioned at all in the section specifically dedicated to double-close prevention.
Likewise, with implicit weakening, nothing stops you from dropping the socket without closing it.
Likewise, with implicit weakening, nothing stops you from dropping the socket without closing it.