Ok, so strictly speaking there is no bug. Both gc and gccgo are
spec-compliant; gc just opts not to raise an error in this case. (One
might say it is a bug that gc doesn't raise the error consistently, but I
don't think the spec says anything about consistency, only optionality.)
In any case, I
Hi Rogue,
On Sun, Jul 3, 2016 at 5:13 PM, wrote:
> It seems i can't edit my original post so:
While it may not look like it from if you use the Google Groups
interface, emails are being sent out in the background when you post
to golang-nuts. So there's no way to edit anything, you can only sen
Thanks Matt.
After your advice (and some reflection) - i decided to refactor all my code
and keep the matrix in colour.Colour values rather than uint32's.
Am actually happier i did it, as it provides for more neater / more concise
code with better readability.
Interestingly though, when i do a
:) Thanks Dan... my mental blank moment (which lasted an hour!) got me! :)
i definitely look a giraffe staring at the headlights now! :)
On Mon, Jul 4, 2016 at 12:27 PM, Dan Kortschak <
dan.kortsc...@adelaide.edu.au> wrote:
> They're packages, not links.
>
> https://github.com/gonum/matrix
> -
On Mon, Jul 4, 2016 at 3:35 AM, mhhcbon wrote:
> Hi,
>
> I have this program which reads file, flate encode then flate decode the
> data.
>
> I noticed that when i used different size for the slice of []byte to read
> data, the program will retain memory when the size is > 16384.
> When its lower
On Sun, Jul 3, 2016 at 8:07 PM, wrote:
> Build Env:
>
> Build tool: GoClipse
> Windows(7):
> Go Installation: go1.6.2 windows/amd64
>
> Under default build environment, every thing goes well. I could find the
> .exe file in bin folder. But if I try to build target for linux with setting
> env
Build Env:
Build tool: GoClipse
Windows(7):
Go Installation: go1.6.2 windows/amd64
Under default build environment, every thing goes well. I could find the
.exe file in bin folder. But if I try to build target for linux with
setting environment:
GOOS=linux
GOARCH=amd64
I will get the fo
On Sun, Jul 3, 2016 at 12:27 PM, Jon Bodner wrote:
>
> I'm working on a DAO adapter layer helper called Proteus
> (https://github.com/jonbodner/proteus), and ran into an interesting quirk in
> what Go considers equivalent interfaces. I recreated a simplified version of
> the issue is at https://pl
On Sat, Jul 2, 2016 at 2:20 AM, wrote:
> More generally, this is https://github.com/golang/go/issues/10989.
>
> Such ineffectual assignments can be detected using
> https://github.com/gordonklaus/ineffassign.
>
> An analysis showed that only a small fraction of such were bugs, making the
> backwa
Matt:
Thanks for you confirmation.
--
Jingguo
--
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...@googlegroups.com.
For more options, visit
Also I am using LetsEncrypt
On Saturday, July 2, 2016 at 5:21:40 PM UTC-7, Constantine Vassilev wrote:
>
> I am using go version 1.6.2 to set up a web page to work with
> http/2.
>
> It is working on desktop but in iOS 9 mobile Safari the site does not
> loads.
>
> Here is my setup:
>
> OS El Cap
Hello,
I'm working on a DAO adapter layer helper called Proteus
(https://github.com/jonbodner/proteus), and ran into an interesting quirk
in what Go considers equivalent interfaces. I recreated a simplified
version of the issue is at https://play.golang.org/p/BS3-bUKtO9 .
The code that I linke
That's correct.
On Sun, Jul 3, 2016 at 7:25 PM Jingguo Yao wrote:
> Take the following code as an example:
>
>
> package main
> import (
> "fmt"
> )
> const (
> First int64 = iota
> Second
> )
> const (
> One int64 = 1
> Two = 2
> )
> func main() {
> fmt.Printf("First type: %T, Secon
My previous example didn't compile because I made a change right before
hitting share. Here's a working version.
https://play.golang.org/p/E3dPLRjFvW
On Sun, Jul 3, 2016 at 7:27 PM Dan Kortschak
wrote:
> They're packages, not links.
>
> https://github.com/gonum/matrix
> - docs: https://godoc.org
They're packages, not links.
https://github.com/gonum/matrix
- docs: https://godoc.org/github.com/gonum/matrix/mat64
https://github.com/go-gl/mathgl
- docs: https://godoc.org/github.com/go-gl/mathgl/mgl64
On Mon, 2016-07-04 at 12:08 +1000, simran wrote:
> Hi Dan,
>
> I get a "page not found" on
I think you're best off not taking the RGBA values and then building a
color from them. Just take the color you're given and use m.Set(x, y, c) on
the target image. If you need to modify the color, one way to do that would
be to create your own object that implements the color.Color interface (the
Take the following code as an example:
package main
import (
"fmt"
)
const (
First int64 = iota
Second
)
const (
One int64 = 1
Two = 2
)
func main() {
fmt.Printf("First type: %T, Second type: %T\n", First, Second)
fmt.Printf("One type: %T, Two type: %T\n", One, Two)
}
Running the
Hi Dan,
I get a "page not found" on all those four links...
cheers,
simran.
On Mon, Jul 4, 2016 at 10:22 AM, Dan Kortschak <
dan.kortsc...@adelaide.edu.au> wrote:
> github.com/gonum/matrix/mat64 (soonish to be gonum.org/pkg/matrix/mat64)
> is a general purpose matrix library.
>
> A more specif
I'm still getting the red's turning to pinks...
You make an interesting point about the format of the source image... i was
assuming that the image/{png,jpeg,gif} packages can read in a file and
whatever the colour profiles were, i could get the equivalent RGBA values
for them (this does appear to
Hi, all
liteide x30 released!
This version bug fix, support go1.7, add fakevim mode (thanks jsuppe
https://github.com/jsuppe) , add quick open files (ctrl+p) and quick open
editor (ctrl+alt+p) actions.
LiteIDE Source code : https://github.com/visualfc/liteide
Gotools Source code : https://github.c
github.com/gonum/matrix/mat64 (soonish to be gonum.org/pkg/matrix/mat64)
is a general purpose matrix library.
A more specific image maths package is available at
github.com/go-gl/mathgl/mgl{32,64}.
On Mon, 2016-07-04 at 10:07 +1000, simran wrote:
> Hi Dan,
>
> I am hoping to find a general matri
This one avoids the type assertion: https://play.golang.org/p/vDB9RboNZj
On Sun, Jul 3, 2016 at 5:11 PM Matt Harden wrote:
> If the source image is an image.RGBA, then the colors are already int8s;
> there's no additional information to lose. Here's an example that swaps the
> green and red chan
If the source image is an image.RGBA, then the colors are already int8s;
there's no additional information to lose. Here's an example that swaps the
green and red channels of the pixel at (0,0):
https://play.golang.org/p/i6F29OsdgD
On Sun, Jul 3, 2016 at 5:08 PM simran wrote:
> Hi Dan,
>
> I am
Hi Dan,
I am hoping to find a general matrix library as i want to write my own
rotation, translation, reflection methods; however, if you do know a good
image library doing these, i'd appreciate it as a reference anyway.
cheers,
simran.
On Mon, Jul 4, 2016 at 10:00 AM, Dan Kortschak <
dan.korts
Hi Matt,
What i want to do is get the r,g,b,a values individually, modify them and
then set them.
Your example was good, but is not extracting the r,g,b,a values
individually (which come out as uint32's), and then say when i change them
and set them again, it complains that it only wants uint8's.
Are you looking for generalised matrices or simply image
rotation/translation/transformation?
On Mon, 2016-07-04 at 02:06 +1000, simran wrote:
>
> Could someone please point me to a good matrix library for Go (i'm
> sure
> something exists, although i can't seem to find it!).
>
> Am hoping to do
Are you looking for generalised matrices or simply image
rotation/translation?
On Mon, 2016-07-04 at 02:06 +1000, simran wrote:
>
> Could someone please point me to a good matrix library for Go (i'm
> sure
> something exists, although i can't seem to find it!).
>
> Am hoping to do some image man
I can't tell exactly what the problem is from your example, but does this
help?
https://play.golang.org/p/AF8UjkG4Ao
On Sun, Jul 3, 2016 at 4:40 PM simran wrote:
> Hi Constantin,
>
> Where i seen the uint8 being defined is at:
> https://golang.org/pkg/image/color/#RGBA
>
> Although the there is
Hi Constantin,
Where i seen the uint8 being defined is at:
https://golang.org/pkg/image/color/#RGBA
Although the there is a method RGBA() which returns r,g,b,a in uint32 the
struct is only uint8's and so i suspect has to be initialised as such.
What i'm finding annoying is that the following fai
Actually that's my mistake. It is spec'ed but not in the bullet points.
https://golang.org/ref/spec#Comparison_operators
Still, I find this hairy.
On Monday, July 4, 2016 at 12:52:11 AM UTC+2, Chad wrote:
>
> To illustrate.
> I think that an issue should be raised.
>
> https://play.golang.org/p/e
To illustrate.
I think that an issue should be raised.
https://play.golang.org/p/eiwG-4vsnJ
--
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+unsubsc
On Monday, July 4, 2016 at 12:09:57 AM UTC+2, as@gmail.com wrote:
>
> I wish I could be pointed to such discussion.
>>
>
> It was briefly discussed in *The Go Programming Language *book by Donovan
> & Kernighan (p 132)
>
> *:*
>
>> An analogous “shallow” equality test for slices could be use
>
> I wish I could be pointed to such discussion.
>
It was briefly discussed in *The Go Programming Language *book by Donovan &
Kernighan (p 132)
*:*
> An analogous “shallow” equality test for slices could be useful, and it
> would solve the problem with maps, but the inconsistent treatment o
I wish I could be pointed to such discussion.
> The language authors omitted this functionality for a reason. One of the
> reasons is that arrays and slices are similar, and changing their
> comparison semantics seemed confusing.
>
https://blog.golang.org/slices specifically mentions that arra
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 o
Sorry for my explanations.
I wanted to mean that when i use a len([]byte) <=16384
the program can read lots of megabytes and remains
at a stable state of memory usage, 5 mb.
When i use higher values, the memory grows and keep growing.
by higher value i mean anything > 16384
The slice is valid
Sorry for bumping an oldish thread, but I just ran into this trying to
propagate an exit code.
I didn't find anything searching that was sufficiently
platform-independent, but a little spelunking into the stdlib source
bore fruit, so I thought I'd share my solution.
If you have an *exec.ExitError
Still t
On Sunday, July 3, 2016, Tristan Colgate
wrote:
> Hi All,
> I'd like to announce hugot. An (hopefully) idiomatic library for
> building chat bots.
> It is inspired by net/http, and hopefully let's you build bots up how
> you want to.
> I'm particularly interested in feedback on the
On 2016-07-03 20:35, mhhcbon wrote:
> r :=buf.Bytes()// read from encoder
> buf.Truncate(0)
I did not understand your explanation of the problem, but surely there
is a bug in the code quoted above.
Read bytes.Buffer Bytes() function documentation:
func (b *Buffer) Bytes() []byte
Bytes returns
Pardon?
On Sunday, July 3, 2016 at 8:13:30 PM UTC+2, as@gmail.com wrote:
>
> 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, Cha
Hi All,
I'd like to announce hugot. An (hopefully) idiomatic library for building
chat bots.
It is inspired by net/http, and hopefully let's you build bots up how you
want to.
I'm particularly interested in feedback on the API. (...and test coverage
is next on my list, promise!)
Hopefully I
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
>
Hi,
I have this program which reads file, flate encode then flate decode the
data.
I noticed that when i used different size for the slice of []byte to read
data, the program will retain memory when the size is > 16384.
When its lower than this value everything is fine, but 16385 breaks.
I don
I cannot answer about the matrix library but the package is consistently
talking about int and not uint8
If you look at the specification https://golang.org/pkg/image/#RGBA.SetRGBA
You can impose 64bit which is not your pupose but apparently truncating int
is not mandatory.
Can you indicate where
Hi All,
Could someone please point me to a good matrix library for Go (i'm sure
something exists, although i can't seem to find it!).
Am hoping to do some image manipulation for which being able to work with
matrices would be great.
Have written simple helper stuff for images (i used to find mys
Complete post is here
https://groups.google.com/forum/#!topic/golang-nuts/eHUauZwcHrg
On Sunday, July 3, 2016 at 5:40:03 PM UTC+2, Constantin Konstantinidis
wrote:
>
> Upgrade to 1.6.2 would be a good idea.
> Similar post is advising to use
> https://go-review.googlesource.com/#/c/24720/ to fix
Upgrade to 1.6.2 would be a good idea.
Similar post is advising to
use https://go-review.googlesource.com/#/c/24720/ to fix similar issues.
On Sunday, July 3, 2016 at 3:57:54 PM UTC+2, power...@163.com wrote:
>
> I failed to build gomobile, here are my steps,
>
> 1. git clone https://go.google
It seems i can't edit my original post so:
There should be "So pointer from slice b is pointing to new array" instead
of "So pointer from slice b is pointing to new slice"
W dniu niedziela, 3 lipca 2016 17:05:06 UTC+2 użytkownik rog...@gmail.com
napisał:
>
> Thx Ian,
>
> So basically it's bec
Thx Ian,
So basically it's because we allocate new array in version without cap,
right? Because it outgrows current cap. So pointer from slice b is
pointing to new slice (i've checked they have different addresses for first
element) different from a.
And in version with cap=10 we still append
On Sun, Jul 3, 2016 at 4:27 AM, wrote:
> Can anyone ELI5 it to me, please ? Why if we remove cap result is different
> ? I don't understand that.
https://blog.golang.org/slices
Ian
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscrib
Can anyone ELI5 it to me, please ? Why if we remove cap result is different
? I don't understand that.
--
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-nu
I failed to build gomobile, here are my steps,
1. git clone https://go.googlesource.com/mobile/
2. cd mobile\cmd\gomobile
3. go build
I got error like
package .
imports golang.org/x/mobile/internal/binres: use of internal package
not allowed
What should I do?
My platform: win10 / amd64 /
Hi,
The link I gave you was to a proposed change to Gomobile to fix your
problem. If you don't know how to apply it, just wait for it to be approved
and submitted. Then, you can simply run the go get and gomobile init
commands again.
- elias
On Sat, Jul 2, 2016 at 8:51 PM JM wrote:
> Sorry, i
Ok. That "haha" was merely to show that no animosity was borne. And also
because you didn't really answer the question as I asked (by quoting the
spec) which I found funny.
Alas, I guess we couldn't see eye to eye.
But chill a little bit. I have given all the hardcoded proofs and people
have j
I'm sorry but your attitude is counterproductive to the discussion.
"haha" what? I told you I see your point, I think I know the specs very
well, thank you for the link.
However, you seem incapable of accepting, despite an number of others
saying the contrary, despite, given a reasonable example
Ok, Let me help you out haha :)
Here is the definition of a slice. It is not a container.
https://golang.org/ref/spec#Slice_types
I am not inventing things.
I know what people on this thread said, but that's their misconception.
On Sunday, July 3, 2016 at 1:40:46 PM UTC+2, Florin Pățan wrote:
>
As you pointed out, Printf() should follow the ref spec but that doesn't
happen because some humans don't perceive this accuracy as necessary or
maybe because the way to resonate about slices / arrays is as containers
for the actual values.
Thus we have Printf working as it does (and %p will ind
In fact, that is somewhat my fault.
I should ask:
What is a slice?
What is an array?
Spoiler: a slice is a reference type in its "wikipedia-ish" definition
(auto-dereferencing) which is the reason you observe such a result in the
playground.
On Sunday, July 3, 2016 at 1:12:17 PM UTC+2, Chad w
No. You should not get it from here. You should get the answer from the
spec. Let alone the fact that the implementation should ideally follow the
spec and not the reverse.
On Sunday, July 3, 2016 at 1:03:44 PM UTC+2, Florin Pățan wrote:
>
> If I look at what %v means, print out the values of va
If I look at what %v means, print out the values of various types in Go,
according to https://golang.org/pkg/fmt/ then I believe that this holds the
answer: https://play.golang.org/p/GiLckoBDxa
On Sunday, July 3, 2016 at 11:33:01 AM UTC+1, Chad wrote:
>
> Not for comparison.
>
> I am just asking
Not for comparison.
I am just asking what is the value of a slice and what is the value of an
array.
Remember that there is no slice comparison that has been spec'ed so far.
On Sunday, July 3, 2016 at 12:24:05 PM UTC+2, Florin Pățan wrote:
>
> For []T the value of a slice for the purpose of com
For []T the value of a slice for the purpose of comparison would be each
individual value compared against each-other (ofc maybe comparing the
length first as an optimization).
Same goes for an array.
And again, you are missing the whole point. Both me and you are wrong in
each-others points of
What's the value of a slice?
What's the value of an array?
On Sunday, July 3, 2016 at 12:05:38 PM UTC+2, Florin Pățan wrote:
>
> If the type is *[]T then comparing memory addresses make sense to see if
> both terms point to the same memory address.
> If the type is []T then comparing memory addr
If the type is *[]T then comparing memory addresses make sense to see if
both terms point to the same memory address.
If the type is []T then comparing memory addresses doesn't make sense as
I'd expect to compare values.
Finally, if the type is []*T then I'd still expect to compare values (even
Which is why it should be formalized.
Where is the inconsistency between slices and arrays?
Why do people even think that a slice need to behave like an array wrt
equality, were it introduced?
A slice is not an array!
On Sunday, July 3, 2016 at 11:36:44 AM UTC+2, as@gmail.com wrote:
>
>
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 work.
Oh, maybe you mistook reference type for the notion of reference.
On Sunday, July 3, 2016 at 9:49:34 AM UTC+2, Martin Geisler wrote:
>
> Hi Chad,
>
> On Sat, Jul 2, 2016 at 10:43 AM, Chad >
> wrote:
> >
> > On Saturday, July 2, 2016 at 10:23:04 AM UTC+2, Martin Geisler wrote:
> >>
> >> On Fr
Rob and Robert actually wrote that this area of the spec needs more work...
Otherwise, the behaviour of maps, slices and funcs cannot be fully
explained.
On Sunday, July 3, 2016 at 7:25:31 AM UTC+2, as@gmail.com wrote:
>
> Go does not have reference types. As far as I know, the word was
> pu
Hi Chad,
On Sat, Jul 2, 2016 at 10:43 AM, Chad wrote:
>
> On Saturday, July 2, 2016 at 10:23:04 AM UTC+2, Martin Geisler wrote:
>>
>> On Fri, Jul 1, 2016 at 4:01 PM, Chad wrote:
>>>
>>> On Friday, July 1, 2016 at 3:44:10 PM UTC+2, Martin Geisler wrote:
I keep seeing references (hah!) to thi
69 matches
Mail list logo
