[go-nuts] [ANN] decundec, a decorate-sort-undecorate package

d. See the decundec package page <https://pkg.go.dev/github.com/spakin/decundec#section-readme> for more information, documentation, and examples. — Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from

Re: [go-nuts] Re: runtime/pprof - pausing CPU profiling

create a runtime CPU profile but to restrict the profile to a specific part of the program. runtime/pprof - pausing CPU profiling To create a runtime CPU profile for a specific part of a Go program, you can use the `runtime/pprof` package. Here's how you can do it: 1. **Import the Package**: Add

Re: [go-nuts] LLM development toolkit.

You might like this dev.to/pullreview/creating-a-remote-git-hub-for-your-companywithout-github-1fdb On Friday, November 8, 2024 at 8:34:55 AM UTC-8 Dimas Prawira wrote: > It is not uncommon to shared go either library or application through git > with zip file, the common way is share the code i

Re: [go-nuts] atomic variables?

*True* *However, it's important to note that in some cases, multiple loads might be necessary for correctness, such as in certain lock-free algorithms or when implementing specific memory ordering requirements* *citation .**W

Re: [go-nuts] Go Regexp debugger?

Thanks for the share Quick reference is a life saver https://regex101.com On Tue, Nov 5, 2024, 5:01 AM Steve Mynott wrote: > I'm aware of https://regex101.com/ which is fine 90% of the time for > debugging go regex, but I did find an edge case where it misled me a > few years back. > > There was

Re: [go-nuts] time.ParseDuration does not accept scientific notation

On Friday, April 26, 2024 at 6:08:02 PM UTC-6 Ian Lance Taylor wrote: The first step would be to open a proposal for this change. See https://github.com/golang/proposal#readme. Thanks. Done: proposal: time: allow scientific notation in ParseDuration

[go-nuts] time.ParseDuration does not accept scientific notation

While parsing output from some third-party program, I discovered that time.ParseDuration does not accept inputs expressed in scientific notation even though strconv.ParseFloat does accept such inputs. Here’s an play

[go-nuts] gomobile bind in win10

0 I am a learner of golang ,trying to use golang to develop android When I want to package into APK, I encounter the following problems I'm following the official guide to install gomobile. OS:Win10 go version go1.20.2 windows/amd64 I have in

[go-nuts] godoc formatting of example test

ng to fix? Thanks, — Scott -- 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. To view this discussion on the w

Re: [go-nuts] Implementation of image.NRGBA64

M UTC-6 Nigel Tao wrote: > On Tue, Sep 28, 2021 at 3:53 AM Scott Pakin wrote: > >> I'm curious: Why does image.NRGBA64 define Pix as a []uint8 and >> perpetually pack pairs of uint8 values into a uint16? Wouldn't it have >> been easier and faster to defi

[go-nuts] Implementation of image.NRGBA64

I'm curious: Why does image.NRGBA64 define Pix as a []uint8 and perpetually pack pairs of uint8 values into a uint16? Wouldn't it have been easier and faster to define Pix as a []uint16 and Stride to be a stride in uint16s rather than uint8s? — Scott -- You received this message b

[go-nuts] Re: A question about Type Sets

Great to see you playing with generics. I'll leave it up to the experts to reply about whether the compilation problems are bugs. But I have a suggestion: don't try to define Vec in an interface with a type set. Just use T[] -- looks like it might simplify things. Scott On Tuesd

[go-nuts] Re: Query on using Closures

Just a guess: You may need to make a local copy of index inside your loop because index gets overwritten each iteration. On Sunday, June 6, 2021 at 12:45:01 PM UTC-6 Suveetha Kamatchi wrote: > Hi team > I am a newbie to golang. > I am writing a code that does transactions in postgres. > The li

Re: [go-nuts] Operator precedence

Axel and Keith: Thanks for responding. I'm glad it sounds like I'm reading the spec correctly—and that Go shouldn't do anything sneaky with evaluation order. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and st

Re: [go-nuts] Operator precedence

Alex and Keith: Thanks for responding. I'm glad it sounds like I'm reading the spec correctly—and that Go shouldn't do anything sneaky with evaluation order. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and st

[go-nuts] How is golang web applications for seo

How are golang web applications on a scale of 1 to 10 for seo rankings? -- 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.

[go-nuts] Operator precedence

hat the language guarantees that a*3.0/2.0 will always be evaluated as (a*3.0)/2.0 and never as a*(3.0/2.0), even though the constant expression can be computed at compile time? Does this hold for integer types, too (e.g., a*3/2)? Thanks, — Scott -- You received this message because you are subscrib

[go-nuts] Re: Compiler treatment of infinite loops

On Friday, March 5, 2021 at 8:20:36 AM UTC-7 Brian Candler wrote: > There is a flip side to that: if you add the return statements, then > ForLoop1() gives an error due to unreachable code! > https://play.golang.org/p/0bajnJWTz7U > > So you can't win either way. I think this implies that if the

[go-nuts] Compiler treatment of infinite loops

The Go compiler (I'm using go1.16 linux/amd64) correctly infers that function with an infinite for { … } loop that conditionally returns a value from within the loop does not also need to return a value at the end of the function: - https://play.golang.org/p/07ZjFx2uJlx However, changing th

[go-nuts] [ANN] New Go package: xmorph

h toy.) The Go package is essentially a wrapper for the C libmorph library ( http://xmorph.sourceforge.net/), which is what the morph CLI and the xmorph and gtkmorph GUIs build upon. Enjoy! — Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts&

Re: [go-nuts] It is said that future Macs will use ARM, is golang ready for this move ?

the speaker making a point that PowerPoint posed a challenge for them because their tool looked for known compiler code-generation patterns that they could exploit for performance (correctness?), but at the time, PowerPoint was hand-coded in assembly language. Imagine! — Scott P.S. I just c

Re: [go-nuts] A modest format suggestion

Ian's and Lutz's responses get to the heart of how comments on parameters are different from comments on struct field, constant and variable initializations, namely that the documentation framework (whether in an IDE or via godoc) elevates comments on functions to a different status than "inter

Re: [go-nuts] A modest format suggestion

ts to be passed to the function, it is > best to redesign it and use a data structure that encapsulates the > arguments. Otherwise, what is wrong with this? > > > // Great is a really great function anArg does this and anotherArg does > that. > func Great(anArg int, anotherAr

[go-nuts] A modest format suggestion

I greatly appreciate the fact that Go has a coding standard. I have a modest proposed modification. Instead of this: // Great is a really great function. func Great( anArg int, // This explains anArg anotherArg string, // This explains anotherArg ) (err error) { ..

Re: [go-nuts] Why isn't there "number plus" postfix syntax for more than or equal?

t; > The “in” part feels important to me. > Python's chained comparison operators are arguably more compatible with the existing Go syntax and semantics, though: 99 <= a <= 128 — Scott -- You received this message because you are subscribed to the Google Groups "golang-n

[go-nuts] Re: HSV image format

On Sunday, March 29, 2020 at 11:30:02 AM UTC-6, Scott Pakin wrote: > > Does anyone know of a package that provides an image.Image > <https://golang.org/pkg/image/#Image> with an HSV color model > <https://golang.org/pkg/image/color/#Model>? I've found lots of &

[go-nuts] HSV image format

ge interface. If not, I'll write my own and make it available, but I figured I should first check if someone has already done this. Thanks, — Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group a

[go-nuts] Re: Writing bitmap data to a canvas with WebAssembly

.3 ± 4.2 on the WebAssembly side plus 6.0 ± 2.3 on the JavaScript side) This is the time to render a simple 800×800 gradient pattern. I hope others find this useful. — Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To u

[go-nuts] Re: Writing bitmap data to a canvas with WebAssembly

10); > > Might not be the most efficient way, but it seems like it should work. > Yes, that definitely sounds like it's worth a shot. Thanks, — Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

[go-nuts] Re: Writing bitmap data to a canvas with WebAssembly

echnique with a ? Thanks for the code. It's good to see that there's a way to skip base64 conversions during the Go-to-JavaScript data transfer. — Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

[go-nuts] Re: Writing bitmap data to a canvas with WebAssembly

here isn't a more direct way—especially in newer versions of Go—to pass image data directly between Go and JavaScript. Regards, — Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receivi

[go-nuts] Writing bitmap data to a canvas with WebAssembly

ll/js/#CopyBytesToJS> function, but I was unable to get that to work because the image data is a Uint8ClampedArray and CopyBytesToJS expects a Uint8Array. I kept trying to populate a Go []byte and transfer that to the image but never succeeded in making that work. Thanks, — Scott -- You r

Re: [go-nuts] Panicking in public API ?

n be handled > programmatically). > Nicely presented guideline! — Scott -- 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...@go

[go-nuts] Re: ? How restrict usage of packages ?

9c37251e1914ad23ad16f5c9e458bc90eddf08a/src/gosp2go/utils.go#L64> . — Scott -- 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...@g

[go-nuts] [ANN] Go Server Pages

sing Go as the programming language and with more thought given to security in the implementation. Here's where to go for documentation and downloads: Home page: https://gosp.pakin.org/ GitHub repo: https://github.com/spakin/gosp Enjoy! — Scott -- You received this message because you are

Re: [go-nuts] sqlserver error "TLS Handshake failed: x509: certificate signed by unknown authority"

on. For example, I use Alpine linux as my Docker base > image for my Go services, and I must install the certificates like this via > the Dockerfile: > > RUN apk update && apk add ca-certificates > > Find the correct way to do that in your Docker base image. > > -- M

[go-nuts] sqlserver error "TLS Handshake failed: x509: certificate signed by unknown authority"

I am using a dockerized Golang image to connect to my Azure SQL server database. When I try to ping it, I am running into "TLS Handshake failed: x509: certificate signed by unknown authority". I am able to run my app from my box without dockerization without any issues. I am also able to able t

[go-nuts] Writing my first Go module

get the latest commit, whatever its version? Thanks, — Scott -- 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...@googlegrou

[go-nuts] GitHub go-formal ownership

feel free to contact Marko with contributions and ideas related to sharing and coordinating work related to formal logic technologies in and for Go. Cheers, Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

[go-nuts] [ANN] Irifrance R&D open on GitHub

open to stewardship by the community. Best, Scott -- 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

[go-nuts] [ANN] Gini sat solver v1.0

darn fast for a CDCL solver in Go, measuring up to standard CDCL C/C++ solvers in a variety of tests. This release corresponds with a dedication of the stewardship of Gini to the community. Please feel free to follow up here on go-nuts or in private reply about how to gain access. Best Scott

[go-nuts] [ANN] Reach -- a symbolic safety model checker

re so welcome, inquiries here on go-nuts or in private reply welcome for github invites. Best, Scott -- 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 golan

[go-nuts] Re: the latest "go install"

+1 On Friday, 25 January 2019 08:53:13 UTC+1, Daniel Skinner wrote: > > This will probably sound stupid, but I think it's important; I recently > tried to install a util I had written in Go that depended on a third party > library and the install simply didn't work. Maybe it's a failure of > re

Re: [go-nuts] GitHub go-formal ownership

necessary imply being a formal tech expert. It might even help to not be an expert so as to avoid bias in inclusion. On the other hand, of course if someone with impressive credentials put their name on it that would help too. Scott On Wednesday, 23 January 2019 13:59:59 UTC+1, Marko Ristin w

[go-nuts] GitHub go-formal ownership

Donavan of the golang analysis packages. 2. GopherSat authors. 3. Others who have worked on formal projects in Go but less visibly. 4. go-critic and staticcheck.io authors. Please do feel free to contact me off-line or here on go-nuts for details. Best, Scott -- You received this message

[go-nuts] Embedded files with WebAssembly

lt;https://github.com/gobuffalo/packr>? Something else? Thanks, — Scott -- 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...@googl

[go-nuts] Re: Defer, clousures and structs

n the context of the defer statement. it will then apply the function to the previously evaluated bar upon function exit (or after other defers if there are any). Hope that helps Scott On Wednesday, 19 December 2018 23:42:01 UTC+1, Victor Giordano wrote: > > Perhaps someone could explai

Re: [go-nuts] Re: GoAWK: an AWK interpreter written in Go

k/ > Thanks for doing the performance analysis of spakin/awk <https://github.com/spakin/awk>! Once I find the time to work on that project some more, I'll certainly look into implementing some of your suggestions. — Scott -- You received this message because you are subscribe

Re: [go-nuts] Re: gomobile: what's the right way to make widgets?

from everything else and I do want Go in general to focus on expanding the scope of where it excels. Scott > > BR fino > > >> It would be nice if cross-platform GUIs were easier to write, but they >> are not. The incentives are all wrong. Platform vendors wan

Re: [go-nuts] Re: Go 2 Proposal Comments

more topic, but it happens. Not sure myself how or if the question of happiness with or without aging gophers is relevant. Scott > > On Sun, 2018-10-28 at 07:31 -0500, Robert Engels wrote: > > Next thing Gophers will be crying for is lambda syntax... just wait. >

Re: [go-nuts] Re: Go 2 Proposal Comments

d. For example, if it were linked while the stack is high/deep, then where would the runtime put the stack? where would the runtime system stack be placed? It's very different than applying a runtime to byte code. Scott > > > Sent from my iPhone > > > On Oc

Re: [go-nuts] Generics: an unwelcome conclusion and a proposal

either use examples or build on a set of standard supplied contracts by embedding. Scott On Wednesday, 17 October 2018 21:57:48 UTC+2, Marvin Renich wrote: > > * Ian Lance Taylor > [181016 17:59]: > > The contract system in the generics design draft does not have this >

[go-nuts] Re: Generics: an unwelcome conclusion and a proposal

On Thursday, 18 October 2018 08:00:56 UTC+2, Beoran wrote: > > After reading his proposal, I think you should help Burak Sedar work out > his proposal in the other thread. > Where is Burak Sedar's proposal? > It is conceptually a lot easier than the idea of contracts, but likely to > be

Re: [go-nuts] Re: gomobile: what's the right way to make widgets?

On Sunday, 28 October 2018 05:13:15 UTC+1, Lucio wrote: > > On Sunday, 28 October 2018 01:58:56 UTC+2, Scott Cotton wrote: >> >> >> [ ... ] >> Then a cross platform App would just implement for each platform. That >> would be more work for app writers

Re: [go-nuts] Re: gomobile: what's the right way to make widgets?

On Saturday, 27 October 2018 23:31:11 UTC+2, Ian Lance Taylor wrote: > > On Sat, Oct 27, 2018 at 7:02 AM, Space A. > wrote: > > > > I wish go2 team would focus on cross-platform GUI rather than > nobody-needed > > generics after all. There is nothing you can do atm, write your own > library

Re: [go-nuts] Q16.16 fixed point numbers in go

, that's close enough for many purposes. But it gets more complicated with carries/rounding and other functions (such as trig). Scott > On Mon, Oct 22, 2018 at 3:24 PM Vasiliy Tolstov > wrote: > >> Thanks for suggestions. >> If somebody can look at github.com/unis

Re: [go-nuts] Re: do you use binary-only packages?

publishes a C library and decides to use Go for part of its implementation should not have to say "we use Go so if you use cgo, then ..." This combination is perhaps hypothetical at this point for Go, but there are low level Rust libraries like this where the consumer doesn'

Re: [go-nuts] Python heapq.merge in golang using channels?

Yes Robert's observation that you need all values to merge sorted data, and that channels don't provide this. However, if the implementation receives on channels ahead of time, then this isn't a problem because you do have one value from each source to decide how to proceed. On Sunday, 21 Oc

Re: [go-nuts] Re: do you use binary-only packages?

don't suffer from these problems in any case (eg plugins). Scott On Friday, 19 October 2018 02:13:01 UTC+2, Tharaneedharan Vilwanathan wrote: > > Hi Ian, > > Good question. I don't have an answer. > > But this raises some questions: > > Should Go be anticip

Re: [go-nuts] Go language should become an ANSI and ISO standard.

I think standards have a tendency to end up failing to be standard because of a plethora of standards, the need to make optional parts which render the standard impractical for basic tasks (eg open al), the fact that large market interests tend to have their own version (eg open SL ES android),

Re: [go-nuts] go:nosplit

On Mon, 8 Oct 2018 at 16:30, Ian Lance Taylor wrote: > On Mon, Oct 8, 2018 at 4:50 AM, Scott Cotton wrote: > Your real concern > has to do with running audio code without interruption. That concern, > too, is abstract. We don't know how well it works today and we don

Re: [go-nuts] go:nosplit

d the runtime doesn't specify what sys calls it might or might not use. So it is not really a question of whether you are using the syscall package correctly or its organisation w.r.t. operating systems. Scott On Monday, 8 October 2018 13:54:26 UTC+2, Jan Mercl wrote: > > On Mon,

Re: [go-nuts] go:nosplit

On Monday, 8 October 2018 06:02:13 UTC+2, Ian Lance Taylor wrote: > > On Fri, Oct 5, 2018 at 11:57 PM, Scott Cotton > wrote: > > > > On Fri, 5 Oct 2018 at 23:26, Ian Lance Taylor > wrote: > >> > >> On Fri, Oct 5, 2018 at 2:10 PM, Scott Cott

Re: [go-nuts] go:nosplit

On Sat, 6 Oct 2018 at 08:57, Scott Cotton wrote: > > > On Fri, 5 Oct 2018 at 23:26, Ian Lance Taylor wrote: > >> On Fri, Oct 5, 2018 at 2:10 PM, Scott Cotton wrote: >> > > >> In fact >> we definitely do want to add other preemption checks that oc

Re: [go-nuts] go:nosplit

On Fri, 5 Oct 2018 at 23:26, Ian Lance Taylor wrote: > On Fri, Oct 5, 2018 at 2:10 PM, Scott Cotton wrote: > > In fact > we definitely do want to add other preemption checks that occur at > points other than function entry (issues #10958, #24543). And if > there is anothe

Re: [go-nuts] go:nosplit

On Sat, 6 Oct 2018 at 02:10, Ian Lance Taylor wrote: > On Fri, Oct 5, 2018 at 3:21 PM, Scott Cotton wrote: > > > > On Fri, 5 Oct 2018 at 23:46, Scott Cotton wrote: > >> > >> Thanks much for the info. > >> > >> Do you have any more pointers abo

Re: [go-nuts] go:nosplit

On Fri, 5 Oct 2018 at 23:46, Scott Cotton wrote: > Thanks much for the info. > > Do you have any more pointers about how one may assess whether or ensure > that a stack overflow check > is not necessary in order to safely use this directive? > Perhaps the compiler automaticall

Re: [go-nuts] go:nosplit

Thanks much for the info. Do you have any more pointers about how one may assess whether or ensure that a stack overflow check is not necessary in order to safely use this directive? Scott On Fri, 5 Oct 2018 at 23:26, Ian Lance Taylor wrote: > On Fri, Oct 5, 2018 at 2:10 PM, Scott Cot

[go-nuts] go:nosplit

the emission/addition of pre-emption instructions in the function it annotates? 3. Can it be used with gccgo? Thanks for any info, Scott -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receivin

Re: [go-nuts] deadlock "runtime.(*sigctx).preparePanic"

gets back to > the go side and this is the most difficult part - not knowing what the > panic actually is. > > My current "workaround" is to timeout the cgo call in my code but I'm > obviously leaking goroutines. > > - Paul > > On Wednesday, October 3,

Re: [go-nuts] deadlock "runtime.(*sigctx).preparePanic"

in alpha, though, and if you try it you will likely need the latest PR which isn't yet merged. Scott On Wednesday, 3 October 2018 10:07:22 UTC+2, Scott Cotton wrote: > > don't know if it's related, but maybe adding below to your callback (from > portaudio callback) will

Re: [go-nuts] deadlock "runtime.(*sigctx).preparePanic"

don't know if it's related, but maybe adding below to your callback (from portaudio callback) will shed some light on your problem defer func() { // Don't let PortAudio silently swallow panics. if x := recover(); x != nil { buf := make([]byte, 1<<10) for runtime.Stack(buf, true) == len(buf) {

Re: [go-nuts] Re: How to setup your development environment using Go modules

about, no extra tools to learn. The disadvantages: probably less flexible. less opportunity to contribute to shared tooling. Hope that helps anyone considering workflows with multiple modules Scott On Sunday, 9 September 2018 21:19:34 UTC+2, thepud...@gmail.com wrote: > > Hi al

Re: [go-nuts] cgo use question

expectations by the OS of what the call should not do are such that go's runtime treatment of cgo->go on the foreign thread is undesirable. So I need to call C without calling by Go //export in this very particular case. Scott On Mon, 1 Oct 2018 at 10:42, Tamás Gulácsi wrote: &g

Re: [go-nuts] cgo use question

topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Scott Cotton http://www.iri-labs.com -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe fr

Re: [go-nuts] Constraints for generics

ea of specifying relations over types by example compelling in general and for Go in particular. Still working on (better) unifying the relation of contracts to interfaces, but that's in no way a rejection of the basic ideas in the contracts draft proposal. Scott > On Sep 30, 2018, at 10:

Re: [go-nuts] cgo use question

nal C dependency for the purpose of using more pure Go and less cgo :) Thanks in any event for your help, it was also informative to me. Scott > -- > You received this message because you are subscribed to a topic in the Google > Groups "golang-nuts" group. > To unsubscribe from t

Re: [go-nuts] Constraints for generics

this later issue, but it's pretty heady stuff and outside the scope of what I want to have to think about when coding, so as to focus efforts more readily on the objective of the code rather than heady type theory. practical operator overloading isn't a solved problem AFAIK, much

Re: [go-nuts] cgo use question

which means I either need to make a C library separately or copy+rename or use static functions fC tand have go get and go modules work. hmm... maybe I'll copy the C code and make the functions static file members. If that's the best solution, it is disappointing :( Scott On Su

Re: [go-nuts] cgo use question

Hi all, For info, short of a solution for linking cgo specific C functions cross package, I think one can do this with C function pointers, which at least is a close approximation of directly calls. Best, Scott On Sunday, 30 September 2018 14:08:28 UTC+2, Scott Cotton wrote: > >

Re: [go-nuts] cgo use question

y, no make, 2 -- cgo C function called by C in more than one package)? Scott On Sun, 30 Sep 2018 at 13:57, Simon Ritchie wrote: > > Write a separate package to handle the C stuff and call it from the other two. > > I built a wrapper for a c++ library: > https://github.com/gob

[go-nuts] cgo use question

g the C functions. My attempts so far have all yielded link errors. Either the C function is undefined in one of the two Go packages (at build or runtime, depending on how I use "extern") or I get multiple symbol definitions. Scott -- You received this message because you are su

Re: [go-nuts] go mod tidy pulls in too much

;sntz=1&usg=AFQjCNF6hRXvDGfAJDpqZUX63pGCvsvm3A> Best, Scott On Saturday, 29 September 2018 15:53:53 UTC+2, Scott Cotton wrote: > > Hi all, > > I think this is related to https://github.com/golang/go/issues/26913 > which is closed but still has commentary that seems unresolved after it was > cl

Re: [go-nuts] go mod tidy pulls in too much

Hi all, I think this is related to https://github.com/golang/go/issues/26913 which is closed but still has commentary that seems unresolved after it was closed . Scott On Friday, 28 September 2018 20:11:29 UTC+2, Harmen wrote: > > On Fri, Sep 28, 2018 at 10:19:50AM -0700, thepud...@gma

[go-nuts] Re: proposal: generic generics proposal

taphysics: not as far as I know :) generic: at least a general way of doing it. Scott > > thanks > Dan > -- 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,

Re: [go-nuts] [ANN] go-formal github organisation

ider type theory formal, as in pure form (like system F, type systems for ocaml) "formal" as well. There are also things like proof carrying code which contains a proof that remote execution is safe in some way. so what "formal" is not formally defined :) Hopefully, this will help

[go-nuts] Re: [ANN] go-formal github organisation

And of course, it's at https://github.com/go-formal On Thursday, 27 September 2018 11:38:08 UTC+2, Scott Cotton wrote: > > Hi all, > > I've just created a github organisation for formal tools in and for Go. > > There's not much there now, but it is open to all t

[go-nuts] [ANN] go-formal github organisation

not secret) github member. Best, Scott -- 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

Re: [go-nuts] Re: Using modules with go test ./...

Hi @thepudds, Good to hear and glad to have followed up so as to have introduced in the conversation how to address the concern in that post. Thanks for the great summary of how to give effective feedback about about modules and the general context. Best, Scott On Saturday, 22 September

Re: [go-nuts] Re: Using modules with go test ./...

flexibility in implementing the statement above from golang.org might allow a more informed basis on which to take modules out of preliminary status. But others may depend on or like modules behaviour like this. I have no way of knowing. Also, yes I agree the listing of the deleted go.mod

[go-nuts] Re: Using modules with go test ./...

a main module. They are marked needs fix and go1.1.2. I think your use case is related. I haven't had a problem with that one because I just set up my workflow to run tests where there are go.mod files. Best, Scott On Thursday, 20 September 2018 21:21:32 UTC+2, John wrote: > > Jus

[go-nuts] go mobile android release?

build). Best, Scott -- 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 https://groups.google.com/d/optout.

Re: [go-nuts] Runtime threads/OS thread scheduling

Thanks all, Indeed useful. Will continue exploring the "it's hard to say" part on golang-dev, as that might be useful as well. Best, Scott On 17 September 2018 at 20:43, robert engels wrote: > Then it should be fairly trivial to call cgo to raise the priority of the >

[go-nuts] Runtime threads/OS thread scheduling

sired scheduling priority/type (as pointed out on a related thread in golang-dev) The question is: does this as of go1.11 interfere with Go runtime internal prioritising of threads? The other question is: may it one day interfere with Go runtime internal prioritising of threads? Best, Scott --

Re: [go-nuts] modules and package cyclic dips

ntly, a prerelease is not a kind of release in the docs on tip.golang.org. Best, Scott -- 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+uns

Re: [go-nuts] modules and package cyclic dips

it? (I would think not, but reading the docs I would think it would update to the alpha) Scott On 16 September 2018 at 16:44, wrote: > Hi Scott, > > Modules do provide support for semver pre-release notation. You can read > more about it in these sections of the documentation, f

Re: [go-nuts] modules and package cyclic dips

find the idea useful and would like to use pre-release info with modules. So can anyone comment, inform, or provide a pointer to some documentation about pre-releases as they relate to modules? Best, Scott On 15 September 2018 at 22:11, Sameer Ajmani wrote: > Thanks. The relationship

Re: [go-nuts] modules and package cyclic dips

lar module are added to the list, > then at the end only the latest version (according to semantic version > ordering) is kept for use in the build." > > > --thepudds > > On Saturday, September 15, 2018 at 6:34:55 AM UTC-4, Scott Cotton wrote:

Re: [go-nuts] modules and package cyclic dips

n it seems to me that is not the intended use case for cycles and that might be undesirable or even lead to the inability of a module maintainer in the cycle to effectively propagate an update. If I come across anything more concrete, I'll file an issue. Just food for thought at this poi

Re: [go-nuts] Re: Go 2 error-handling counter-proposal: returnfrom

rvativism causing headaches for real code, only for contrived examples. If it's really not possible to make compile-time detection work, I'd say that the returnfrom in f should exit the goroutine but not return its argument from g. This is consistent with the case of returning from a con

  1   2   >