[go-nuts] Re: [ANN] astits: parse and demux MPEG Transport Streams (.ts) natively in GO

Hey guys, A user in Reddit asked a good question and I'm interested in the answer you may have. The question was "Has anyone looked at how this package compares to https://github.com/Comcast/gots?;. Initially I've used this package to parse MPEG transport streams, but I didn't really like the

[go-nuts] chan chan Job per worker vs. single chan Job

Hi! This should be covered somewhere already but I can't find it. So here's my question: Assume N workers running in a goroutine each and a number of Job tasks coming in. The consensus appears to be to have one dispatcher goroutine collecting all jobs, then pulling a ready worker from a

Re: [go-nuts] Help me MVC golang

Please describe the error you are getting. (I suspect this me yet-another “go run”-episode) It seems you are trying to do MVC the ASP.NET way in Go - I’m quite confident that this will not give a good result. I’ve been down a similar route (pun intended) when I started

[go-nuts] Re: f*ck you, golang

The PHBs always want FORTRAN IV programmers, in any language. Just lie and say Go was written by FORTRAN experts. Lik Kernighan and Pike, for example. --dave > On Friday, July 24, 2015 at 12:19:29 AM UTC+2, Roberto Zanotto wrote: >> >> I have to work on a project for an university exam and

Re: [go-nuts] Introspecting a type

That's nice work-around! Thank you Jakob! Best regards, :) Hein On Wednesday, November 22, 2017 at 11:27:34 PM UTC-8, Jakob Borg wrote: > > A variable of type [][]Operation has that type and only that type. Your > Concurrent and Sequential types are convertible to []Operation, and this is >

[go-nuts] Re: various odd, to me, at best undocumented, behaviour of automatic formatting in go doc

what you are describing is what i expected from the start, a form of duck-typing, in that if it looks like a Title then format it as a Title, fine, simple and efficient. i don't expect all the cases where the documentation is wrong that could easy, simply and usefully not be. -- You received

[go-nuts] Re: f*ck you, golang

> I was meant to be a successful C++/Java programmer, now that is ruined > forever. [...] > My life is ruined and it's on you. You can only blame yourself. You should have studied for the exam rather than doing extra-curricular stuff. -- You received this message because you are subscribed

Re: [go-nuts] How to get explicit receiver of a method through reflect?

If you knew the representation of the function, and how captured variables were stored in this representation, you could use unsafe to reinterpret the function value as a usable form (pointer, tuple, whatever) and de-reference this data to read captured variable addresses. In the case you

[go-nuts] Re: Would someone care to compare Firefox Quantum Rust concurrency features to Go....

Concurrency in Rust and Go are completely different things. In Rust a thread has its own memory space and hence a thread cannot reference data by reference of some other thread. The rational behind that is security. Also, a thread in Rust is not lightweight, but a full-blown OS thread. So there

[go-nuts] Help me MVC golang

-- Blog -|---Controllers ---|---Backend ---|index_controller.go ---|---Frontend ---|index_controller.go -|-main.go /// file main.go package main import ( "net/http"

[go-nuts] Re: Interest in implementing dual-pivot or 3-pivot quicksort for faster sorting?

Did a quick translation of the implementation https://github.com/egonelbre/exp/tree/master/sorts/qpsort The implementation seems to fail some Go tests. --- FAIL: TestSortBM (0.00s) sort_test.go:168: n=100 m=1 dist=stagger mode=copy: used 840 swaps sorting slice of 100 --- FAIL:

[go-nuts] Re: f*ck you, golang

On Friday, July 24, 2015 at 12:19:29 AM UTC+2, Roberto Zanotto wrote: > > I have to work on a project for an university exam and the professor > highly recommends doing it in C++ with (his) FastFlow library. Now, because > of Go, I can't stand looking at object oriented code anymore. The way

[go-nuts] Re: various odd, to me, at best undocumented, behaviour of automatic formatting in go doc

On Wednesday, 22 November 2017 19:09:46 UTC+1, simon place wrote: > > trying to work around these issues, i find another undocumented 'feature' > > https://play.golang.org/p/dzcq5XKpgG > > It is the same logic: A heading is a heading to a normal text paragraph. Lines are not headings by

[go-nuts] Would someone care to compare Firefox Quantum Rust concurrency features to Go....

How would this look, if implemented in Go? Is there anything to learn from Rust "fearless concurrency"? What are the goals and complexity trade-offs of the two languages? https://blog.rust-lang.org/2017/11/14/Fearless-Concurrency-In-Firefox-Quantum.html When and why would there be a browser