Re: [go-nuts] Guaranteeing deterministic execution of Golang code

This is a very strange discussion. I don’t understand the purpose. Malloc() isn’t even deterministic. Which means any arbitrary program can take the address to generate entropy regardless of having time, etc available. I didn’t look it up, but I’m pretty sure there is a “law” that if the langu

Re: [go-nuts] Guaranteeing deterministic execution of Golang code

On Mon, Jan 16, 2023 at 12:38 AM Stan Srednyak wrote: > hi Axel, > > thanks for sharing. Why did you mention webassembly specifically, why not > go or c? > I mentioned WebAssembly specifically because a) it has a well sandboxed, single-threaded VM and b) there are existing compilers for Go. I do

Re: [go-nuts] Guaranteeing deterministic execution of Golang code

hi Axel, thanks for sharing. Why did you mention webassembly specifically, why not go or c? Stan On Sat, Jan 14, 2023 at 6:37 PM Axel Wagner wrote: > Oh, also, fmt: https://go.dev/play/p/xxOw3vqWR4u (probably need to run > this offline) > > Honestly, I don't think there really is a practical w

[go-nuts] Re: What do you think of a tar package?

Yes, there is a lot of problems with it. Mainly it is so low level that it needs hundreds of lines of code to make something of feature parity even with the simplest bsdtar not to mention gnutar. On Thursday, November 26, 2009 at 1:45:53 AM UTC-5 j-g-faustus wrote: > There is already a tar pac

Re: [go-nuts] Guaranteeing deterministic execution of Golang code

Sorry, I should have read Axel's blogpost before posting. I enjoyed reading it, thanks for sharing :) some of what I was talking about is covered with more code examples in the post. On Sunday, January 15, 2023 at 1:03:50 PM UTC-7 Kevin Chowski wrote: > I think a little more background about t

Re: [go-nuts] Guaranteeing deterministic execution of Golang code

I think a little more background about the context of the question would be helpful. Determinism may mean different things in different situations depending ont he guarantees you need. Also, did you know that the go playground (play.golang.org) is intended to be generally deterministic so that

[go-nuts] etcd, how to stop it ?

Hi All ! I do understand that my question is not quite in the right arrea, but frankly, I'm totally lost. I'm not able to find the answer for the looks like very simple question. How to run - yes there is a sample, but how to stop it ? Thank you. -- You received this message because you are sub

[go-nuts] go-flags

I'm trying to learn how to use the go-flags package from github. When I do: go get github.com/jessevdk/go-flags, I'm getting the error below, and I don't understand why go get: module github.com/jessievdk/go-flags: git ls-remote -q origin in /home/rob/go/pkg/mod/cache/vcs/911474c21097b0efc171a3

[go-nuts] Re: marshalling array of bson.M

You will probably get more help if you provide the relevant details, such as which bson package you are using. And provide an *example *that shows what you have tried that produces the error. A playground link using the "share" button is the preferred way to include examp

Re: [go-nuts] when doing a WalkDir of a FileSystem, how do you get access to the path that you are working on

Hi! On Sat, 14 Jan 2023, Pat Farrell wrote: > On Saturday, January 14, 2023 at 6:52:15 PM UTC-5 raf wrote: >> The function you implement (WalkDirFunc should receive "p" as the path to >> the parent (that seems to be what you want) and "d" as the current >> directory entry. I am not sure why in