On Saturday, January 25, 2020 at 9:46:19 AM UTC+1, Eric Raymond wrote:
> [...]
> An early reviewer pointed out that if the Go code were an entire
> function it could be expressed something like this:
>
> ---
>
> func pipeline(source T)
On Monday, January 27, 2020 at 11:18:50 AM UTC+1, Manlio Perillo wrote:
> [...]
>
> What about introducing a support type. As an example (not tested)
> https://play.golang.org/p/WkHyEI52xKu
>
>
Here is an updated version of the Pipeline type, with error handling:
https://play.golang.org/p/Qs6_fI
Dear golang-nuts,
As https://github.com/golang/go/issues/27151,
https://github.com/golang/go/issues/6853 and many relevant issues
discussed, Go download is huge.
The Go download contains everything in the main repo. Since Go modules are
now a success, is it considered to separate all runtime i
2020. január 27., hétfő 12:27:35 UTC+1 időpontban changkun a következőt
írta:
>
> Dear golang-nuts,
>
> As https://github.com/golang/go/issues/27151,
> https://github.com/golang/go/issues/6853 and many relevant issues
> discussed, Go download is huge.
>
> The Go download contains everything in t
I find it, thank you.
在 2020年1月27日星期一 UTC+8下午2:30:03，Ian Lance Taylor写道：
>
> On Sun, Jan 26, 2020 at 5:48 PM jin wang > wrote:
> >
> > Thank you very much, it's a fact that he change was 6 years ago, it's a
> pity can't get that benchmark code.
>
> You can get the benchmark code; the benchma
It makes some sense, thank you very much.
在 2020年1月27日星期一 UTC+8下午12:50:32，changkun写道：
>
> 256 run queue size is designed for the work-steal scheduler to prevent
> false sharing.
>
> 128 run queue size exactly fits one cache line. Since the run queue can be
> stolen half of the run queue from the
>
> but the others are needed for "go build" & co.
>
This can be solved by first issuing an std module first, then using go
modules to import these packages for go build.
The idea is to separate compiler and runtime, then have a minimum go core
distribution. The Go development process then can
On Monday, 27 January 2020 12:27:35 UTC+1, changkun wrote:
>
> Dear golang-nuts,
>
> As https://github.com/golang/go/issues/27151,
> https://github.com/golang/go/issues/6853 and many relevant issues
> discussed, Go download is huge.
>
Neither of these issues benefits from splitting the stdlib fr
> > log.Fatal and os.Exit have the same problem. They are not "terminating
> > statements", so if you want them at the bottom of a function with result
> > parameters you have to add a panic("unreachable").
>
> Excellent point. But contemplating being able to declare library functions
> termina
The original message mentions size. The given list is 25MB/337MB
uncompressed or 7MB/115MB compressed. So in terms of saved space, we are
talking ~6%. It's not nothing, but it's also not a lot. Especially as
you'll most likely need to download them right after anyway.
You also mentions splitting u
Sorry for the false alarm -- I found a workaround (building the tour
locally) which seems to solve my problem here:
https://github.com/golang/tour/issues/866
git clone https://github.com/golang/tour.git
cd tour
go build
go install
tour
Don't know how I missed that issue yesterday. Posting this
Hi All,
Good Afternoon.
My name is Kareem.
I recently started learning GO on my own.
I am going through the book "INTRODUCTION TO GO" from RIELY.
I wrote a program to convert Degrees to Fahrenheit. It is as follows:
*package main*
*import "fmt"*
*func main () {*
* fmt.Println("Enter the d
On Mon, Jan 27, 2020, at 02:41, Kareem Shaikh wrote:
> Can anyone please tell me what should I change in order to get the right
> output?
>
> For example:
>
> I want to change 10 degrees to Fahrenheit.
> I want to print "10 degrees to Fahrenheit is = 50"
You want to use one of the formatting fu
Hi all!
Asking for the help of the community because I haven't been able to find
the answer on my own.
I'm writing an http fuzzer in go and was implementing a proxy options from
the cli.
My use case is that I want all the requests to be sent to the proxy when
the flag is set. No matter if it's
On Sunday, January 26, 2020 at 10:27:35 PM UTC-8, pentel...@gmail.com wrote:
>
>
> IMHO, golang didn't make a dent on key areas to become a language of
> choice like big data (analytics, complex event processing, etc.) and
> consequently, hot topics like artificial intelligence. Exactly areas wh
On Monday, January 27, 2020 at 11:16:12 AM UTC-5, Sam Whited wrote:
>
> On Mon, Jan 27, 2020, at 02:41, Kareem Shaikh wrote:
> > Can anyone please tell me what should I change in order to get the right
> output?
> >
> > For example:
> >
> > I want to change 10 degrees to Fahrenheit.
> > I
Python, to its credit, has the nice inclusive property of extensible
interpreters of being friendly to "hang things" onto just like ornaments on
trees. By linking with C/C++-libraries and adding glue/shim code, anything
can be used from Python. This facility and interpretive execution (as Eric
John
On Monday, January 27, 2020 at 9:51:43 AM UTC-5, Philip Boampong wrote:
>
> I assumed the ugliness is about the recover logic being exposed in the
> catch signature and in the handler function. If you change catch to
> take the exception handler as a callback you can hide the recover
> logic w
Hi!
I'm writing a bittorrent private udp tracker and now the bittorrent
standard changed to ed55519 crypto
to encrypt connections.
How use ed19 with crypto/tls package? i'm a newbee in crypto/tls,
too.
all examples and hints are wellcome! :-)
Very Very Very Thanks in Avance!
Developer: not sure this is going to work... use Python for POC
SVP: Looks great! Ship it!
Developer: but wait...
> On Jan 27, 2020, at 11:05 AM, Michael Jones wrote:
>
>
> Python, to its credit, has the nice inclusive property of extensible
> interpreters of being friendly to "hang things" o
Kareem,
Here is an example,
package main
import "fmt"
func main() {
fmt.Println("Enter degrees Celsius (℃): ")
var celsius float64
fmt.Scanf("%f", &celsius)
var fahrenheit float64
fahrenheit = ((celsius * 9) / 5) + 32
fmt.Printf("%.2f℃ is %.2f℉\n", celsius, fahrenheit)
}
I appreciate the concern at the possibility that "mindshare" is decreasing and
would rather read of such than not in order to take that into consideration. So
I appreciate your message. But I do wonder what a similar source would say
about YAML. I imagine the chart would be relatively flat, yet
Michael Jones :
> Python, to its credit, has the nice inclusive property of extensible
> interpreters of being friendly to "hang things" onto just like ornaments on
> trees. By linking with C/C++-libraries and adding glue/shim code, anything
> can be used from Python. This facility and interpretive
Go mindshare suffers if it's seen as worse for prototyping, and necessary
only for scale. Especially as there are more efficient (albeit more
complex) ways to achieve scale.
On Mon, Jan 27, 2020, 10:55 AM Eric S. Raymond wrote:
> Michael Jones :
> > Python, to its credit, has the nice inclusive
easy prototyping != scaling
Pick one.
> On Jan 27, 2020, at 1:42 PM, Liam Breck wrote:
>
>
> Go mindshare suffers if it's seen as worse for prototyping, and necessary
> only for scale. Especially as there are more efficient (albeit more complex)
> ways to achieve scale.
>
>> On Mon, Jan
On Mon, Jan 27, 2020 at 7:02 AM 'Axel Wagner' via golang-nuts
wrote:
>
> The original message mentions size. The given list is 25MB/337MB uncompressed
> or 7MB/115MB compressed. So in terms of saved space, we are talking ~6%. It's
> not nothing, but it's also not a lot. Especially as you'll most
I'm just a "rando" from the peanut gallery, but over the past 2 years I've
nearly *always* been able to find bindings with which to "hang things on" a
Go-based prototype, if indeed it wasn't already in the stdlib.
So golang has become my 'go-to' for prototyping, replacing Python entirely
for new w
Doesn’t this piggyback on making the runtime a shared library so it can be
updated without application recompile?
> On Jan 27, 2020, at 2:24 PM, Ian Lance Taylor wrote:
>
> On Mon, Jan 27, 2020 at 7:02 AM 'Axel Wagner' via golang-nuts
> wrote:
>>
>> The original message mentions size. The gi
On Mon, Jan 27, 2020 at 1:27 PM Robert Engels wrote:
>
> Doesn’t this piggyback on making the runtime a shared library so it can be
> updated without application recompile?
I guess I'm not sure what you mean. That already works today, for
people who choose to use it. It seems independent of ho
I have so far not migrated towards the new go modules. I am beginning the
process. Looking for ideas.
I split my applications into indepe
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails f
Oops. That was messed up.
I have so far not migrated towards the new go modules. I am beginning the
process. Looking for ideas.
I split my applications into independent packages each in its own directory.
the structure might look like:
top/src
/pkg1
/pkg2
the imports are bas
I've received a feeler about a most interesting reposurgeon-related
consulting engagement from the company that currently owns the historical
Unix sources. I'm not going to go into the gory details in a public forum
as they might be considered company confidential, but it gives me reason
to as
What I am referring to is a Go shared runtime library, that my Go executable
would link against at runtime, so that if I compile my Go program against
1.13.0 it will run against any 1.13.x stdlib Go runtime installed by the client.
This way for security patches, only new runtimes need to be ship
There are instructions on how to bootstrap the toolchain in here:
https://golang.org/doc/install/source
Look for "Bootstrap toolchain".
-- Raffaele
On Mon, Jan 27, 2020 at 4:20 PM Eric Raymond wrote:
>
> I've received a feeler about a most interesting reposurgeon-related
> consulting engagement
Hello Srini,
There is a decent answer covering some points on how to structure your module,
options on where to place your go.mod file, and how to arrange your packages
within a module here:
https://stackoverflow.com/a/57314494
One thing to note is that it says in that answer that you cann
On Mon, Jan 27, 2020 at 4:22 PM robert engels wrote:
>
> What I am referring to is a Go shared runtime library, that my Go executable
> would link against at runtime, so that if I compile my Go program against
> 1.13.0 it will run against any 1.13.x stdlib Go runtime installed by the
> client.
Take a look at these blog articles:
https://blog.golang.org/using-go-modules
https://blog.golang.org/migrating-to-go-modules
Lutz
Von: golang-nuts@googlegroups.com im Auftrag von
R Srinivasan
Gesendet: Dienstag, 28. Januar 2020 00:29
An: golang-nuts
Be
37 matches
Mail list logo
