Re: [go-nuts] Returning a JSON object saved as a string in a database

Hi Shawn, Thank you for your quick reply! I’m not having any issues retrieving data from the database. I’m only concerned that the unmarshalling and marshalling processes seem needless and a little risky especially on big JSON objects. On Thursday, August 10, 2017 at 1:17:02 PM UTC-7, Shawn

Re: [go-nuts] Returning a JSON object saved as a string in a database

But then if the JSON is sent as a string property of a bigger object, it'll have to be parsed by JavaScript on the browser side. That is undesirable. On Thursday, August 10, 2017 at 1:21:54 PM UTC-7, Shawn Milochik wrote: > > On Thu, Aug 10, 2017 at 4:20 PM, Dmitriy Cherchenko

Re: [go-nuts] Returning a JSON object saved as a string in a database

wrote: > > On 10 Aug 2017, at 22:11, Dmitriy Cherchenko <dcher...@gmail.com > > wrote: > > What is the best way to send the stringified JSON object from the database > as JSON and not as a string-type value of a property in the bigger JSON > object the server is respond

Re: [go-nuts] Re: Named or unnamed struct initialisation? What is best practice?

Can you do a test to see if there's a performance difference? -- 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] Guarantees about evaluation order but not slice indexing

The second possibility you described is exactly what I’m worried about. But I have several places where I’m doing something like b.data[b.grow()] = bt and wouldn’t want to break that up into two lines everywhere. I was wondering if you could find anything else in the spec to guarantee that the

[go-nuts] Guarantees about evaluation order but not slice indexing

It looks like the language spec is a little imprecise in the Order of evaluation section about if any function evaluating an index of a slice will always be invoked before anything is done to the slice at that index. That is, if you have

[go-nuts] Re: Go 1.10 is released

I like how the Go team isn't trying to support very old operating systems. We should focus on modern systems and expect people to try to stay up to date. Thank you! On Friday, February 16, 2018 at 11:36:22 AM UTC-8, Andrew Bonventre wrote: > > Hello gophers, > > We just released Go 1.10. > >