022 at 10:20:47 AM UTC Jan Mercl wrote:
> On Wed, Jan 5, 2022 at 11:09 AM Brieuc Jeunhomme
> wrote:
>
> > But here ,since under non-windows platforms, I can't import the package,
> it means I have to define wrappers for everything I use: types, constants,
> functions.
&
ay, January 4, 2022 at 7:51:25 PM UTC kortschak wrote:
> On Tue, 2022-01-04 at 08:29 -0800, Brieuc Jeunhomme wrote:
> > Hi,
> >
> > I'm writing code that uses the golang.org/x/sys/windows/svc package.
> > This package compiles only for windows builds, for other G
Thank you for your answer. In case someone else is interested, the answer
I was looking for was: the Dialer struct has an optional Control member,
that the user can set. It's a a function that will be called before the
connect() syscall is issued, allowing to set whatever socket options before
Hi,
I'm writing code that uses the golang.org/x/sys/windows/svc package. This
package compiles only for windows builds, for other GOOS values, I get a
build error. That's fair, but I'm wondering how to unit test the code that
calls svc functions when working on a non-windows environment. So
Hi,
looking at the net package of the standard library, I don't see a way to
set the tcp max segment size. Surely, one can create a tcp connection
manually and set the segment size by using the syscall package, but that
approach prevents them from reusing higher level packages that want a
net
