Yes, that makes sense. Thank you.
The example I wrote was concocted. But I've seen others do it on their own
types too, which didn't make sense at all. Maybe they were just
copy-pasting similar code from elsewhere.
On Saturday, 14 September 2019 20:20:49 UTC+5:30, Ben Burwell wrote:
>
> On S
There’s a pure Go (no cgo needed) regexp engine that supports lookahead and
lookbehind here: https://github.com/dlclark/regexp2
However, and I say this as someone who maintains that regex library, use this
type of regex with caution. I would highly recommend changing your code to use
the nativ
On Sat, Sep 14, 2019 at 12:40 AM Durga Someswararao G
wrote:
>
> I tried to execute one regular expression with regex package. When I try to
> compile I am getting unsupported Perl syntax. After reading regex syntax
> conclusion is golang not supporting some combination regex patterns like
> po
Update ugorji to v1.7 works for me
--
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 web vi
Can you explain more specifically what you don't understand?
The example seems pretty clear: Say you currently require the latest master
commit (e.g. by using a pseudo-version), which is a couple commits ahead of
the latest released version, then "latest" will select the release, while
"upgrade" wi
On Sat Sep 14, 2019 at 1:43 AM Sathish VJ wrote:
> I saw some code where there is a temporary type called *noMethod* created
> before performing custom marshaling.
>
> What is the purpose of doing this?
>
> type T struct {
> A int
> C string
> }
>
> func (t T) MarshalJSON() (text []byte, err
You're better off funnelling everything into a single channel.
There's little real difference between reading from one channel that N
things write to, and reading from N channels that have one writer each.
--
You received this message because you are subscribed to the Google Groups
"golang-nu
On Tuesday, September 10, 2019 at 2:48:25 PM UTC+2, Darko Luketic wrote:
>
> What used to work pre go 1.13 now doesn't work anymore
>
> go mod is one big mess no one needs and complicates everything
> I'm now getting ambiguity. How do I resolve it?
> Nothing compiles anymore
>
> ✘ darko@wrk ~/go
I saw some code where there is a temporary type called *noMethod* created
before performing custom marshaling.
What is the purpose of doing this?
type T struct {
A int
C string
}
func (t T) MarshalText() (text []byte, err error) {
type noMethod T
return json.Marshal(noMethod(t))
}
func
The doc https://golang.org/cmd/go/#hdr-Module_queries says:
The string "upgrade" is like "latest", but if the module is currently
> required at a later version than the version "latest" would select (for
> example, a newer pre-release version), "upgrade" will select the later
> version instead.
On Sat, 14 Sep 2019, 07:32 Antoine Mercadal, wrote:
> Hey,
>
> Then why is it called mvs? I don't understand what package system would
> give me 1.3.49, if I require 1.2.0 and my dependency requires 1.1.0.
>
Any time you don't understand why the versions have resolved in a
particular way, I'd re
Hi,
I tried to execute one regular expression with regex package. When I try to
compile I am getting unsupported Perl syntax. After reading regex syntax
conclusion is golang not supporting some combination regex patterns like
positive lookahed,negative lookahed etc. Is there any alternative or
12 matches
Mail list logo
