Re: [go-nuts] Is this algorithm viable? its faster than AES256 upto 50KB

67cb-d7da-4c41-a8c5-92727d24e773n%40googlegroups.com > <https://groups.google.com/d/msgid/golang-nuts/1c8a67cb-d7da-4c41-a8c5-92727d24e773n%40googlegroups.com?utm_medium=email_source=footer> > . > -- Nathan Fisher w: http://junctionbox.ca/ -- You received this message because you

Re: [go-nuts] Thread safe tree library?

to have references available for further research? On Tue, Jan 5, 2021 at 20:15, K. Alex Mills wrote: > On Tue, Jan 5, 2021, 6:59 PM Nathan Fisher wrote: > >> Does write only locking provide read correctness? I would’ve thought >> based on the memory model it could cause i

Re: [go-nuts] Thread safe tree library?

Does write only locking provide read correctness? I would’ve thought based on the memory model it could cause issues? https://golang.org/ref/mem#tmp_2 On Tue, Jan 5, 2021 at 19:40, K. Alex Mills wrote: > That is the simplest and most conservative way go about it, but ultimately > it depends

Re: [go-nuts] import a file

medium=email_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@google

Re: [go-nuts] political fundraising on golang.org!

receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/CA%2BYjuxu%3DYzT6mWA1EtThjf8rTjMfefGmfuzYw__0LwMou4W2wQ%40mail.gmail.com > <https://groups.google.com/d/msgid/golang-nu

Re: [go-nuts] Facebook web app and go?

stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Nathan Fisher w: http://junctionbox.ca/ -- You received this message because you are subscribed to the Google Groups "golang-nu

[go-nuts] Re: Should SIGTERM be included in the os package?

Go convention for variable names (e.g. Interrupt). Whereas the syscall package uses a convention more akin to C (e.g. SIGINT) presumably a result of auto-generation or legacy. On Tue, 16 Apr 2019 at 23:36, Nathan Fisher wrote: > Hello, > > Currently the *os* package defines the followin

[go-nuts] Should SIGTERM be included in the os package?

hile it's simple enough to add a var to my app it feels unnecessary for something that seems an increasingly common signal to handle. Thoughts? Kind regards, -- Nathan Fisher w: http://junctionbox.ca/ -- You received this message because you are subscribed to the Google Groups "golang-nu

Re: [go-nuts] Forking/transfering a repository and import paths

TLDR > Is it possible to fork a repo and change the import path of the repository? Not in one step with the github “click to fork”. You need to do one of the following: 1. Create a new empty remote repo, remap imports, and push to the new remote. 2. Fork, update imports, push. 3. Assuming

Re: [go-nuts] Re: Go assembly interface calls

One trick I’ve used when writing algorithms that use SSE is write it in Go first, run go build to output the assembler for the function, and then tweak the output manually. On Sat, Dec 15, 2018 at 09:36, Jason E. Aten wrote: > reflect.Method(i) and reflect.MethodByName("myFunc") have got to be

Re: [go-nuts] Go offline development recommendations

We use dep at work and commit the vendor folder. The main benefit we see is that it ensures consistent builds across machines, tends to be faster, and allows offline development. assuming you don’t have to use a third party security or infrastructure team to download the dependencies. If you do

Re: [go-nuts] Re: go language sensitive editor?

Agree on this. Gorename and gofmt etc provide only a small subset of what is on GoLands roadmap. I toggle between vs code, vim(-go), and GoLand. There’s bits I like about all 3 but if I had to choose only one I’d probably go with GoLand. On Tue, Nov 20, 2018 at 20:24, robert engels wrote: > I

Re: [go-nuts] Heap of structs

Is there a specific issue you’re experiencing in trying to implement it? Suggestions/observations: - export the struct (Str instead of str) if you’re exporting the Heap. - same for the fields in the struct unless you have a constructor function (eg New) and appropriate functions to modify/view

Re: [go-nuts] go1.11 no longer supports compressed hostnames in SRV lookup replies

Can you share examples? On Wed, Aug 29, 2018 at 19:08, wrote: > We are using SRV records in Kubernetes for various purposes and Go 1.11 no > longer supports compressed names in SRV resource data ( >

Re: [go-nuts] Re: Measure Memory Fragmentation

Do you mean wrt to Go or more generally? I could see using a histogram with a logarithmic bucket size or similar. Where the bucket sizes are the maximum length in bytes a given “open slot” can hold and the count is the number of occurrences of that size in the pool. On Sat, Apr 28, 2018 at 6:18

Re: [go-nuts] Flutter and golang

Oh that’s awesome! I didn’t realise they were supporting desktop now. It sounded like it was abandoned in a push to focus on the mobile experience. On Sat, Mar 10, 2018 at 4:36 PM, Ged Wed wrote: > I used QT for 6 months and Flutter is way ahead. > QT has a huge licensing

Re: [go-nuts] Re: Proposal: return if any not nil

I think for me the benefit of a new statement is that it doesn't result in changes to existing formatting/behaviour. Rather it provides a familiar syntax and style semantic and results in no change to an existing code base (e.g. it's opt in). The problems I see with allowing 1 liner conditionals

[go-nuts] Proposal: return if any not nil

Hi All, I've been contemplating alternative methods to address the "boiler plate" of error handling in Go. One of the main benefits I see to the current approach is that indentation highlights exception paths vs the success path. From a readability perspective I can see the benefit of this

[go-nuts] net/http 404 error handling

Hi All, I came across this issue on GitHub relating to 404 handling in which Brad F. said net/http will not implement templating. https://github.com/golang/go/issues/10707 Perhaps a silly question but why not change http.NotFound into a function pointer like this: ``` var NotFound = func(w

Re: [go-nuts] Re: Understanding garbage collection in Go with infinite lists

Hi Yota, I don't disagree there's value in understanding how Go handles the scenario. What I'm not certain of is the potential tradeoffs when optimising for an uncommon edge case. The loop you've created is very tight and would be unusual to find in a typical application. The allocator is moving

Re: [go-nuts] Re: fmt: Why Golang doesn't have fmt.Printlnf?

I would speculate it's a conscious tradeoff to keep the function count low given it's an equivalent number of characters. On Wed, 8 Feb 2017 at 03:32, 高橋誠二 wrote: > yes, I know but other languages support it as default, isn't it? > > 2017年2月8日水曜日 12時31分00秒 UTC+9

Re: [go-nuts] Re: type assertion: Can I DRY this up?

I guess it becomes a question of what operations you want to do on the data. If you look at the implementation of the Json package and sort interface it might provide you with some approaches to achieve what you want. Json demonstrates reflection, sort demonstrates how to invert the problem in a

Re: [go-nuts] What 5 things does Go need in 2017?

s/hilarious/sad/ If I had a pound for every time I've had to create custom packages/repos for various languages, libraries and apps... I could buy myself a fancy dinner or two. Mon, 12 Sep 2016 at 08:21, Dave Cheney wrote: > Distros are always out of date, sometimes

Re: [go-nuts] Re: Dynamic type cloning

It sounds like you could do something similar-ish to the way sorting is handled in the sort package with interfaces. Some immediate concerns that jump out wrt a read and partial update that is done outside the data source: - partial update implies some form of locking (either optimistic,

Re: [go-nuts] goimports has been updated

+1 to this. Would a vendor folder make sense at the same level as the src folder? Make it an override able default. I guess it doesn't address a monorepo approach though or the collocation of generated files like client/server stubs for protobuf/thrift/etc. On Fri, 15 Jul 2016 at 22:30, Dave

Re: [go-nuts] Plurality of package naming

gt; > Go does not have "objects" in the sense of that post. A Go interface, for > example, does not "have lots of instance variables, lots of arguments, and > pass lots of data around probably." > > A class is not a struct is not a Go interface. > >

Re: [go-nuts] Plurality of package naming

There's a good oop blog article on the caveats of naming classes (struct) ending in -er. http://objology.blogspot.co.uk/2011/09/one-of-best-bits-of-programming-advice.html?m=1 I know the reader/writer interface kind of flies in the face of this but I think that's partly associated with it being

Re: [go-nuts] Re: Singleton pattern for a client handle

complex to stub out and doesn't make dependencies explicit. On Fri, 1 Jul 2016 at 08:14, <krmaya...@gmail.com> wrote: > does the singleton variable for any reason need to be a pointer ? > > > On Thursday, June 30, 2016 at 4:07:08 PM UTC-7, Nathan Fisher wrote: > >> I of

Re: [go-nuts] Re: Singleton pattern for a client handle

I often put all of my wire-up in main which ensures that it's only one instance. Then I create a struct that all of the dependencies hang off of like loggers and clients. On Thu, 30 Jun 2016 at 23:30, Val wrote: > Indeed. > I find it weird that the authors care more about