Thanks for suggesting the Reader(q0, q1 int64) io.RuneReader. I accidentally
replied off list.
I wasn't aware of up to four horsemen being involved. The man pages didn't
prepare me for this.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
Author did a range over channel without select, making cancellation
impossible without closing the channel or the process. However, author
challenges user to solve cancellation problems with no selection, even
saying he awaits for the user to accomplish this. So author will stop
waiting when
I'm sure this has been done already, but I thought I'd share my
implementation of this here for anyone interested in using structural
regular expressions in Go. It doesn't cover 100% of what Edit does in Acme,
but its close enough that I can use the example program
Threads are the structural and functional loci of execution on some operating
systems, data stored in a box accessible to each thread makes sense when you
obey the constraint that the things in that box are to be used for that thread
exclusively.
Goroutines are different, they function like
I also dont want to see context everywhere. At the same time, I don't want it
to be obfuscated in a confusing way.
ctx is an unfortunate initialism and context.Context package stuttering doesn't
help.
I suppose you could stuff a pointer on the stack pointing to a potential
context and then
I'm hesitant to accept generics due to the fear of *overloaded operators *being
the next big deal*. *C# even has *properties (user-defined methods
dispatched upon an assignment operation)*.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To
This information is actually stored in the git commits themselves. There is
a zlib'd field that contains the author's name and email address for each
commit in the repo. A complete transcript for every commit can be
reconstructed from a git repo in this manner.
On Saturday, July 15, 2017 at
It's not ready for general use, but it certainly isn't dead. I think a lack
of examples for some of the more-complex widgets is probably where it needs
the most help, but considering that only one person is working on it the
result is a very impressive addition to the Go ecosystem. I've not
I haven't seen this either, the solution depends on what platform you're
trying to support.
I have a package that does this, for Win32. If you're using Windows, you
use the the Rect() or ClientAbs() in my package to get the position of the
window (or the client area).
I don't use the site, nor understand how any immediate conflicts of interest
can manifest based on the CEO's actions that justify removing the subreddit or
locking it down.
Why not add a community to the official golang.org site and let the subreddit
die of natural causes? It would be a
It's shorter, but it's harder for me to grasp what it does as easily as the
first example.
On Wednesday, August 10, 2016 at 2:09:58 AM UTC-7, Anmol Sethi wrote:
>
> You can shorten that by 6 lines
>
> package main
>
> import "net/http"
>
> func main() {
> http.ListenAndServe(":8080",
I was being facetious. You have the right to opine, but elevating opinions
to that of proofs doesn't give the discussion any utility. I think you
should consider the underlying assumptions in some of your points:
1. A slice is a descriptor of an aggregate
2. A struct can resemble a descriptor
Hardcoded proofs should be assigned well-named identifiers. If you ever
have to alter them, you don't want to be rummaging around your lemmas and
corollaries.
On Sunday, July 3, 2016 at 5:32:26 AM UTC-7, Chad wrote:
>
> Ok. That "haha" was merely to show that no animosity was borne. And also
>
Relaxing unformalized behavior makes little sense to me. Explaining why
equality is inconsistent between slices and arrays is not something I want
to do either.
On Sunday, July 3, 2016 at 1:40:19 AM UTC-7, Chad wrote:
>
> Rob and Robert actually wrote that this area of the spec needs more
Go does not have reference types. As far as I know, the word was purposefully
removed from the spec to remove the ambiguity surrounding the word.
https://groups.google.com/forum/m/#!topic/golang-dev/926npffb6lA
--
You received this message because you are subscribed to the Google Groups
If the distribution builders can take it out, what is preventing them from
adding their own documentation?
On Monday, June 20, 2016 at 9:06:26 PM UTC-7, Joshua Chase wrote:
>
> Yep, that's exactly what I'm saying.
>
>
>
Have you tried to *go get golang.org/x/tools/go/ssa *?
On Wednesday, June 15, 2016 at 10:54:05 AM UTC-7, JW Bell wrote:
>
> >>I have to say that I don't see a big benefit to mirroring a github
> repo on github itself.
> There isn't another way to use the ssa package.
>
> On Tuesday, June 14,
Thanks!
On Monday, June 13, 2016 at 3:27:51 AM UTC-7, Jesper Louis Andersen wrote:
>
>
> On Mon, Jun 13, 2016 at 1:58 AM, wrote:
>
>> What research or other literature can you recommend on the topic of type
>> theory?
>
>
> Benjamin C. Pierce's "Types and Programming
18 matches
Mail list logo