Another approach: https://play.golang.org/p/vTVE3nrGs86
On Friday, 28 May 2021 at 19:00:11 UTC+1 seank...@gmail.com wrote:
> maybe something like https://play.golang.org/p/z-Yp4bh7jto
>
> On Friday, May 28, 2021 at 6:59:34 PM UTC+2 manlio@gmail.com wrote:
>
>> On Friday, May 28, 2021 at
* Pawan Kumar [210528 12:43]:
> Hi Team,
>
> I was using slice function to extract last 2 characters in go template but
> not able to do ,as -ve range is not supported by slice function .
>
> For example - My cluster name is turbo-ab-03 , i can extract if i know
> exact length of cluster
maybe something like https://play.golang.org/p/z-Yp4bh7jto
On Friday, May 28, 2021 at 6:59:34 PM UTC+2 manlio@gmail.com wrote:
> On Friday, May 28, 2021 at 6:26:46 PM UTC+2 sharathc...@gmail.com wrote:
>
>> QuoteToAscii converts non printable characters to \xd , but i literally
>> want the
On Friday, May 28, 2021 at 6:26:46 PM UTC+2 sharathc...@gmail.com wrote:
> QuoteToAscii converts non printable characters to \xd , but i literally
> want the same value .
>
> QuoteToAscii will not produce the json compatible string or will not
> escape string in true sense like
>
> Conversion
Hi, I don't know if this is the correct place to post this kind of
requests, but I wanted to spread the word about an ongoing issue on delve,
which is support for ARM32 targets
https://github.com/go-delve/delve/issues/2051
A bounty on bountysource.com was created to incentivise developers,
To be very exact, this case would actually cause a fault, and is a good
example of why manual management here is best not allowed:
```go
func loop(someSlice []int) {
for _, x := range someSlice {
use(x)
markDelete(x)
}
}
```
Even though you specified for x := range ..., inside the
Hi Team,
I was using slice function to extract last 2 characters in go template but
not able to do ,as -ve range is not supported by slice function .
For example - My cluster name is turbo-ab-03 , i can extract if i know
exact length of cluster name.
{{ slice (index .ServiceMeta
QuoteToAscii converts non printable characters to \xd , but i literally
want the same value .
QuoteToAscii will not produce the json compatible string or will not escape
string in true sense like
Conversion of "abc\u001d" will be converted to "abc\x1d" which is not
compatible with json string
I would be interested if you found an easy solution here... I've been
searching for how to do this currently.
On Saturday, January 16, 2021 at 8:27:42 PM UTC-5 jayesht...@gmail.com
wrote:
> Dear gophers,
>
> Anybody have experience in creating gh-pages and hosting godoc generated
> static
IMO, if we change it, we should change the ";" into ", while". I think
natural language is better than formatted bullet points.
On Fri, May 28, 2021 at 1:45 PM NieomylnieJa wrote:
> Thank you for your responses. While I'm convinced that `ParseInLocation`
> works as intended and I do get that
Thank you for your responses. While I'm convinced that `ParseInLocation`
works as intended and I do get that UTC is an unambiguous zone, the only
thing I still have problem with is with the way this is phrased in the
docs. I had 5 of my colleagues looking at it and none of us has had clarity
On Fri, 28 May 2021, at 11:32 AM, NieomylnieJa wrote:
> But the docs state something different:
>
> // ParseInLocation is like Parse but differs in two important ways.
> // First, in the absence of time zone information, Parse interprets a time as
> UTC;
> // ParseInLocation interprets the time
On Fri, May 28, 2021 at 12:32 PM NieomylnieJa wrote:
> But the docs state something different:
>
> // ParseInLocation is like Parse but differs in two important ways.
> // First, in the absence of time zone information, Parse interprets a time as
> UTC;
> // ParseInLocation interprets the time
But the docs state something different:
// ParseInLocation is like Parse but differs in two important ways.
// First, in the absence of time zone information, Parse interprets a time
as UTC;
// ParseInLocation interprets the time as in the given location.
// Second, when given a zone offset or
yes, i immediately got the point(it is far different from golang ) after i
type these words.
so sorry to disturb
On Friday, May 28, 2021 at 3:39:25 PM UTC+8 Jesse McNelis wrote:
> On Fri, May 28, 2021 at 4:51 PM cheng dong wrote:
>
>> Thank you for the clarification.
>> sorry to break the
On Fri, May 28, 2021 at 4:51 PM cheng dong wrote:
> Thank you for the clarification.
> sorry to break the general rule, i'm new to golang-nuts
>
> as to the question, i figured out i used wrong words, what i need in fact
> is1. a hint to tell compiler that some object are safe to alloc on
Thank you for the clarification.
sorry to break the general rule, i'm new to golang-nuts
as to the question, i figured out i used wrong words, what i need in fact
is1. a hint to tell compiler that some object are safe to alloc on stack(in
case that we use it as interface so it escape from stack)
17 matches
Mail list logo
