[Bug d/91916] Maybe a dead code in socket.d

[rguenth at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91916

Richard Biener  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

[Bug d/91916] Maybe a dead code in socket.d

[ibuclaw at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91916

--- Comment #3 from ibuclaw at gcc dot gnu.org ---
(In reply to Martin Liška from comment #2)
> @Iain: ping^2

Hi, sorry for the late pick-up, I guess the dead code must come from this line.

https://github.com/dlang/phobos/blob/25f38e4b7f2eb4814198ef38dbc44b6ac7b92f78/std/socket.d#L3248-L3251

And whoever wrote the std.socket interface decided to mix multiple different C
enums into one type, so of course there'll be a clash between values.

It does serve to confuse if someone passes a non-time related socket option to
that particular get/setOption override, as the exception message will point to
another value than the one they have actually passed.  There is otherwise no
risk of there actually being any problem in production code.

[Bug d/91916] Maybe a dead code in socket.d

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91916

Martin Liška  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2020-01-23
 Ever confirmed|0   |1

[Bug d/91916] Maybe a dead code in socket.d

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91916

--- Comment #2 from Martin Liška  ---
@Iain: ping^2

[Bug d/91916] Maybe a dead code in socket.d

[marxin at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91916

--- Comment #1 from Martin Liška  ---
@Iain: ping