Really? How would you implement math.Max with generics?
Thomas
On Wed, Jun 22, 2016, 5:45 AM Viktor Kojouharov
wrote:
> https://golang.org/pkg/math/ and https://golang.org/pkg/container/ are
> just two stdlib packages that would greatly benefit from some kind of
>
Yes, truncating the digits (instead of rounding) indeed explains it.
Thanks Austin!
On Wed, Jun 22, 2016 at 5:30 PM, Austin Clements wrote:
> I think what you're seeing is simply rounding in the values printed by the
> gctrace. You're correct that the two metrics are reporting
Hi,
I'm looking at GC statistics using both GODEBUG=gctrace=1 and
debug.ReadGCStats. My question is: should the pause durations reported
in debug.GCStats match the sum of the two STW phases listed in the
gctrace?
I ask because they are generally close but not the same. I have a
trivial program
Permitting symlinks inside GOPATH would introduce all the problems of one
source package having multiple locations that currently plague users of the
vendor/ feature.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this
tgui-harm looks pretty interesting, I'll have to check it out this weekend.
> Go is a very neat programming language, but it is not particulary
fast. On my rather old computer a sampling frequency of 44100Hz caused
problems, but 24000Hz did work
my package dasa.cc/snd defaults to 44100 sample
I'm noticing that if I accidentally create a second template with the same
name but no content there is no error reported when I "parse" it, but then
when I attempt to execute it I do see an error:
https://play.golang.org/p/Rj3433vvju
Is this expected behaviour? Why wouldn't it simply return
Ø Symlinks and the go tools should be avoided.
Was this done intentionally? If so, why? If not, is it a bug which should be
fixed?
John
John Souvestre - New Orleans LA
From: golang-nuts@googlegroups.com [mailto:golang-nuts@googlegroups.com] On
Behalf Of Dave Cheney
Sent: 2016
On Wed, Jun 22, 2016 at 6:37 PM, wrote:
> Hello,
>
> I created a (kind of) organ or piano, to be played with a MIDI keyboard.
> It has a GUI running in the terminal, thanks to the excellent termbox-go
> library. It's only for Linux, but porting should not be too difficult.
>
I should've realized go automatically coerced float constants to ints. Which is
worse but never mind :-)
> On Jun 22, 2016, at 8:57 AM, Jan Mercl <0xj...@gmail.com> wrote:
>
> On Wed, Jun 22, 2016 at 5:54 PM Bakul Shah wrote:
>
> That can be dealt with an output format.
On Wed, Jun 22, 2016 at 5:56 PM Andy Balholm wrote:
> The same is true of brace styles :-P.
Brace style is a matter of preference. Wrong digit grouping in a given
place on Earth is wrong, not less preferred.
--
-j
--
You received this message because you are
On Wed, Jun 22, 2016 at 5:54 PM Bakul Shah wrote:
That can be dealt with an output format. Just as the hex or octal or the
"e" input format is lost.
> ... in Go there is a slight inconsistency: 1e6 is an int but 1e-6 is a
float.
The literals 1e6 and 1e-6 are both untyped
The same is true of brace styles :-P.
But my point is that by not allowing digit grouping, Go avoids style debates on
that issue. The grouping could have been standardized with gofmt, but as it is,
it is standardized by the compiler to a format that is universally understood
(no grouping).
That can be dealt with an output format. Just as the hex or octal or the "e"
input format is lost.
With respect to the "e" notation Go seems to be an exception. Perhaps the sole
one? Other prog languages I have used treat eas a floating pt. even
in Go there is a slight inconsistency: 1e6 is an
Actually, the mention of gofmt brings up the issue of consistent formatting. If
underscores in numbers were allowed, gofmt should automatically insert them for
all numbers over a given length, and remove them for shorter numbers. Otherwise
it would just be another opportunity for inconsistency,
Sorry, I sent that too soon.
One argument against underscores in numbers and other discardable syntax is the
tooling in Go to parse and regenerate go code, as in gofmt. It may be more
complicated to keep the “original input format” around and that is a pretty
good argument—unless that is
> https://github.com/golang/go/issues/42
Michael Jones
michael.jo...@gmail.com
> On Jun 22, 2016, at 7:29 AM, Roger Pack wrote:
>
> Could you drop me a link to the discussion by chance? Seems this
> feature is actually a reasonably common request :)
--
You received
FWIW this is not a failure, just a double define... and if the problem
is in mingw-w64 then it won't be fixed in golang any version of
course, though I'm not sure if that's the case or not.
Cheers!
On Wed, Jun 22, 2016 at 6:24 AM, wrote:
> I am having the same issues
Could you drop me a link to the discussion by chance? Seems this
feature is actually a reasonably common request :)
On Tue, Jun 21, 2016 at 12:47 PM, Michael Jones wrote:
> I asked for this a while back ("drop underscore between digits as in Ada")
> and the answer was
Thank you very much for your response, I think that at abstract level it is
true.
When we go into more detail, we will that GO optimize to have Routine context (
that some kind of Thread context), I think that at the conception level it some
kind of yeild (conception ) to start to GORoutine.
On Wed, Jun 22, 2016 at 6:50 AM, Manlio Perillo
wrote:
> On Wed, Jun 22, 2016 at 3:35 PM, Henrik Johansson
> wrote:
>> Really?
>
> Yes.
> The problem is that many people coming from C like languages may
> incorrectly assume that i is a floating
Really? I find that counting digits in large numbers is harder, for me at
least, than expected. The scientific notation is sweet.
On Wed, Jun 22, 2016, 14:57 Manlio Perillo wrote:
> Il giorno martedì 21 giugno 2016 18:35:13 UTC+2, Caleb Spare ha scritto:
>>
>> This was
On Tuesday, June 21, 2016 at 9:56:21 PM UTC-4, Lazytiger wrote:
> Thanks for all the replies. I agree that there is a better way to do the
> security jobs. I ask this question just for curiosity, to find out if there
> is a equivalence way to do this in golang. From all the replies I assume
>
>> The fact still remains that unlike a lot of other proposed languages
additions that are immediately dropped, generics are still open for
discussion by the language developers themselves.
I think that the problerm only in the Go developers brcause them even does
try to implement them
On Tuesday, June 21, 2016 at 10:29:37 AM UTC-4, Henry wrote:
> You still haven't provided any argument why generics is indispensable.
That can't be the litmus for language feature inclusion; if it was, Go would
resemble ASM.
In my personal experience, something North of 50% of my non-trivial
On Wednesday, 22 June 2016 15:32:53 UTC+3, Andrew Mezoni wrote:
>
> >> The version without generics is necessary to compare how well a
> particular generics approach improves the current language and code.
>
> I am sorry but this is obviously that any useful feature (in the context
> of solving
Il giorno martedì 21 giugno 2016 18:35:13 UTC+2, Caleb Spare ha scritto:
>
> This was shut down without much discussion at
> https://github.com/golang/go/issues/42.
>
> I agree that it's a nice feature.
>
> By the way, though, one nice aspect of Go is that because of how
> untyped constants
On Tuesday, June 21, 2016 at 9:56:01 PM UTC+3, Axel Wagner wrote:
>
> The issue is, that a "KeyValuePair" (no matter if you implemented it
> via generics or like you mention via interfaces) is a fundamentally useless
> type and generics encourage people to add useless types. A
Thank you very much.
I understand that _arm.go file means DO BUILD ONLY ARM PROCESSOR.
2016년 6월 22일 수요일 오후 9시 39분 25초 UTC+9, Jan Mercl 님의 말:
>
> On Wed, Jun 22, 2016 at 2:32 PM wrote:
>
> > How this "magic" can be occurred?
>
> The magic is described here:
>
oh, bad news... I was expecting this to be fixed in 1.7...
On Wed, Jun 22, 2016 at 10:33 PM wrote:
> I am having the same issues with go1.6.2... I also tried go1.7beta2 with
> no luck.
> C:\Go\pkg\tool\windows_amd64\link.exe: running gcc failed: exit status 1
>
>
I think that the idea of Goroutine come from
[https://en.wikipedia.org/wiki/Coroutine], the number of Goroutines are
mapped to OS Threads. In my own opinion, Go maintain the Thread pool and
task queue to dispatch the job.
This pattern has been implemented in some modern JEE container.
Hope
Hi. I have a question about relation between building source code and its
filename.
When I try to build with *store_arm.go* file, I cannot build(compiler
ignore this file).
But after *just change filename of same source code*, it is built.
How this "magic" can be occurred?
Hello Vladimir,
Is there any further developement on goflow? I see that it has last updated
since Nov 7, 2015.
Are there any further intergration in goflow with noflo-ui?
On Tuesday, February 14, 2012 at 4:18:23 AM UTC+10:30, Vladimir Sibirov
wrote:
>
> I'm glad to announce GoFlow package:
>
>> The version without generics is necessary to compare how well a
particular generics approach improves the current language and code.
I am sorry but this is obviously that any useful feature (in the context of
solving problems) improves the current language and code.
Another question: how new
* raidopah...@gmail.com [160621 18:02]:
> I have encountered some unexpected and inconsistent behavior with type
> switches. Can someone shed some light as to why Go behaves this way?
>
> Take a look at https://play.golang.org/p/YPV5YPtWF8
>
> I would expect both of the
>> You are not bringing anything new to the table here, except the attempt
to insult my intelligence, apparently.
>
>
I do not have any claims to anyone personally.
I only defend my own point of view.
P.S.
Also I don't love to see or use some (not my own) code which written like a
mess.
If I
You are not bringing anything new to the table here, except the attempt to
insult my intelligence, apparently.
There are huge software projects out there written in languages that are
less type safe than go and the vast majority of code written is not
reusable. Both also aren't absolutes. There
Sorry for typo and possible spam but correct example here:
type Foo interface {
Get(key K) V
Set(key K, val V)
}
func foo() (int, Foo) {
// Typo: foo := {}
foo := {}
// ...
foos := []Foo{}
// ...
k := "London"
// ...
return
And my point is and was: It doesn't *need* to be both type safe *and*
reusable, unless you are focusing your energy on writing frameworks or
treating type safety as a goal solely for it's own sake. It's perfectly
fine to write small stuff yourself (for example like this) with explicit
types and
>> perfectly type safe.
Perfectly type safe but not perfectly reusable.
What If we slightly complicate the task?
Now is my code and I want to see on your code exampe (perfectly type safe
but and perfectly reusable)
type Foo interface {
Get(key K) V
Set(key K, val V)
}
func foo()
Thanks Krzysztof that was the issue. For cloning the repo I used:-
git clone https://github.com/jabong/florest/
So in mac my code checked out in a directory florest. But the actual repo
name was https://github.com/jabong/floRest/ and in code it was referenced as
floRest which was causing the
40 matches
Mail list logo