> but not really an answer. I was asking if there is some meaning for this
value.
oh, sorry, i misunderstood your question.
the returned value from the network method of the net.addr interface can be
used to pass to connection setup and endpoint resolving functions as an
argument. at that poin
The docs state “Network returns the address's network name, "ip+net".” which is
accurate but not really an answer. I was asking if there is some meaning for
this value. If it was just “ip” this would actually make more sense to me
because it would indicate that TCP and UDP were both supported,
the docs on the network method of ipnet mentions "ip+net".
--
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 opti
hi,
sorry to come back so quickly, after those last updates about memory
management optimizations,
i want to share those latest optimizations about the cpu and some
thoughts...
the results are good, on this configuration, compared to the bounded.go.
the solution consists of a new type of strea
The Network function of the various Addr types in the "net" package
sometimes returns the string "net+ip". I don't see any description of this
value and the my best guess is that it is saying that the address is an IP
network address (from the ip) and it is a network address (from the net)
but
On Thu, Feb 14, 2019 at 2:13 AM Jingguo Yao wrote:
>
> https://blog.golang.org/context uses the following code to cancel the request
> if ctx.Done is closed before the goroutine exits:
>
> func httpDo(ctx context.Context, req *http.Request, f func(*http.Response,
> error) error) error {
> //
Sigh, I see your point. One of those ugly issues where the standard allows
a whole range of values but in reality people only ever use one specific
value. But you don't want to hard code something because of the standard.
--
You received this message because you are subscribed to the Google Gr
looking back:
https://stackoverflow.com/questions/2627511/why-do-c-compilers-prepend-underscores-to-external-names
On Thu, Feb 14, 2019 at 8:54 AM Manlio Perillo
wrote:
> As far as I know, Go currently does not have a list of "reserved" variable
> names, however some tools that generate code do
As far as I know, Go currently does not have a list of "reserved" variable
names, however some tools that generate code do use special names to avoid
potential conflicts.
As an example, stringer add a "_" prefix to each variable.
I don't remember where, but I have seen variable names with a "_"
On Thu, Feb 14, 2019 at 5:33 AM wrote:
>
> Hi,
>
> Am quite new in go language and asking for help.
> I have this JSON object in mongodb with collection name "COLLECTION",
> I have multiple object in the database (mongo) and would like to access all
> the string
> values """apiVersionInUri": "str
select {
case highVal := <- high:
case lowVal := <- low:
if len(high) > 0 {
for len(high) > 0 {
highVal := <- high
}
}
// process lowVal
}
On Tuesday, July 24, 2012 at 5:16:16 AM UTC+8, Erwin Driessens wrote:
>
> Hello,
>
> i
Hi,
Am quite new in go language and asking for help.
I have this JSON object in mongodb with collection name "COLLECTION",
I have multiple object in the database (mongo) and would like to access all
the string
values """apiVersionInUri": "string", in all the objects.
Can anyone help me do this i
I don't get it. Why are they supposed to be dropped only because the
logging service is down?
Making a service between P and the logger is an interesting way to go
>
Another service which could be down then as well? Why not a Queue?
Am Donnerstag, 14. Februar 2019 10:05:40 UTC+1 schrieb Michel
If you need to drop, then a logging goroutine on a channel that writes the log,
and all logging callers select with default drop on that channel.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving e
https://blog.golang.org/context uses the following code to cancel the
request if ctx.Done is closed before the goroutine exits:
func httpDo(ctx context.Context, req *http.Request, f func(*http.Response,
error) error) error {
// Run the HTTP request in a goroutine and pass the response to f.
Hello everyone, thx for all your interesting answers!
I think the fact that when the logger's down, the requests have to be
dropped (not queued, maybe I was not clear enough about that in my first
message) restrains our possibilities. Making a service between P and the
logger is an interesting way
Nice work, you need to add Kotlin, Scala, Hadoop, Redis, MongoDB, Kafka,
Spark, ... :-)))
Am Donnerstag, 14. Februar 2019 00:15:49 UTC+1 schrieb agabo...@gmail.com:
>
> I would love to be able to include your logo as part of our inventory
> (sticker site) but aren’t sure of the restrictions rega
17 matches
Mail list logo