Re: [go-nuts] Makefiles for Go Programs

On Mon, Aug 23, 2021 at 06:12:43PM -0700, Michael Ellis wrote: > Three cheers for mage . It's more verbose than make > but it's pure Go. I use it to build and test projects that include > generated html/css/js supported by a Web Assembly clients communicating > with a ser

Re: [go-nuts] Makefiles for Go Programs

Three cheers for mage . It's more verbose than make but it's pure Go. I use it to build and test projects that include generated html/css/js supported by a Web Assembly clients communicating with a server. On Monday, August 23, 2021 at 7:33:10 PM UTC-4 Connor Kuehl wrote

Re: [go-nuts] Makefiles for Go Programs

> On Aug 22, 2021, at 10:11 PM, jlfo...@berkeley.edu > wrote: > > > I've noticed that few, if any, Go programs use Makefiles. Is that because the > overhead of using make is greater than the overhead of just always compiling > and linking everything? > One piece of evidence for this is tha

[go-nuts] Re: A question about Type Sets

Great to see you playing with generics. I'll leave it up to the experts to reply about whether the compilation problems are bugs. But I have a suggestion: don't try to define Vec in an interface with a type set. Just use T[] -- looks like it might simplify things. Scott On Tuesday, August 2

Re: [go-nuts] Re: Problem with 0MQ and goLang on Windows

On Tue, Aug 24, 2021 at 8:55 AM Dominique Kande Vita wrote: > > Hi All, > > this is a kind of old problem. I am dropping here my solution, just in case > someone will search for as crazy all over the net. > 1. add in your PATH (environement variable) the bin folder where vcpkg has > compiled the

[go-nuts] A question about Type Sets

Hi golang-nuts, I am trying out the latest type parameter and type sets design. The purpose is to implement a Clamp function that works for numbers and vectors. The version for numbers is straightforward and easy: ```go // Number is a type set of numbers. type Number interface { ~int | ~int8 | ~

Re: [go-nuts] Makefiles for Go Programs

> On 23 Aug 2021, at 05:11, jlfo...@berkeley.edu wrote: > >  > I've noticed that few, if any, Go programs use Makefiles. Is that because the > overhead of using make is greater than the of just always compiling and > linking everything? Most likely, it’s because go comes with it’s own buil

[go-nuts] Re: Problem with 0MQ and goLang on Windows

Hi All, this is a kind of old problem. I am dropping here my solution, just in case someone will search for as crazy all over the net. 1. add in your PATH (environement variable) the bin folder where vcpkg has compiled the dll 2. install libsodium via vcpkg 3. copy the dll : libczmq.dll, libso

[go-nuts] A Question About Type Set and Parameter Design

Hi golang-nuts, I am trying out the latest type parameter, and type sets design. The purpose is to implement a Clamp function that works for numbers and vectors. The version for numbers is straightforward and easy: ```go // Number is a type set of numbers. type Number interface { ~int | ~int

Re: [go-nuts] Re: Makefiles for Go Programs

I think the basic idea is that Go projects do not have makefiles because they do not need makefiles. Ideally the Go command does the right thing, including fetching and building dependencies, and building entire trees of projects. Go is opinionated, and dictates where each package can be found

Re: [go-nuts] Re: Makefiles for Go Programs

On Aug 23, 2021, at 12:48, Roland Müller wrote: > > What are the alternatives to Makefile that are used by Go developers? Please > comment :-) Well, there’s mage, which aims to more or less replace the functionality of Make for Go. I’m not really sold on *needing* a replacement for Make, and i

Re: [go-nuts] Re: Makefiles for Go Programs

*** Roland Müller [2021-08-23 19:47]: >What are the alternatives to Makefile that are used by Go developers? >Please comment :-) The best thing I saw, that literally completely changed my life is DJB's redo build system. I replaced everything related to Makefile in all my projects, gaining simplic

Re: [go-nuts] Re: Makefiles for Go Programs

Dnia 2021-08-23, o godz. 19:47:47 Roland Müller napisał(a): > What are the alternatives to Makefile that are used by Go developers? https://github.com/magefile/mage yw. -- Wojciech S. Czarnecki << ^oo^ >> OHIR-RIPE -- You received this message because you are subscribed to the Google Group

Re: [go-nuts] Re: Makefiles for Go Programs

Am Mo., 23. Aug. 2021 um 18:48 Uhr schrieb jake...@gmail.com < jake6...@gmail.com>: > On Sunday, August 22, 2021 at 11:11:23 PM UTC-4 jlfo...@berkeley.edu > wrote: > >> >> I've noticed that few, if any, Go programs use Makefiles. Is that because >> the overhead of using make is greater than the ov

[go-nuts] Re: How much longer

Hi DR, If your students see the web site only through your stream, or if you are in control of the students' browsers (because, for example, it is a live classroom training with computers provided by the school), you can use a browser plugin like uBlock Origin that lets you block specific conte

[go-nuts] Re: Makefiles for Go Programs

On Sunday, August 22, 2021 at 11:11:23 PM UTC-4 jlfo...@berkeley.edu wrote: > > I've noticed that few, if any, Go programs use Makefiles. Is that because > the overhead of using make is greater than the overhead of just always > compiling and linking everything? > Go had built in build caching

Re: [go-nuts] Makefiles for Go Programs

On Aug 22, 2021, at 23:11, jlfo...@berkeley.edu wrote: > >  > I've noticed that few, if any, Go programs use Makefiles. Is that because the > overhead of using make is greater than the overhead of just always compiling > and linking everything? > One piece of evidence for this is that the Go c

[go-nuts] Re: Coverage Reports

See https://kenanbek.medium.com/go-tests-with-html-coverage-report-f977da09552d On Saturday, August 21, 2021 at 3:26:41 AM UTC+7 ivan.rosal...@gmail.com wrote: > Hi, > > > > Anybody knows how I can get a coverage report, ever if the > unit test was failed, when run go test comm