Re: [go-nuts] Noob question: Pointers to interfaces

tl;dr; version don't write generic code -- write concrete code, but do automate the boilerplate stuff... Now depending on the reasons why you want to use ECS there can be several solutions: two easy solutions: 1. https://play.golang.org/p/Vv2yYpMitg 2. https://play.golang.org/p/RCImpkDWT2 *PS

Re: [go-nuts] Noob question: Pointers to interfaces

Sounds like it's also more than a map[type]interface{} and more like either map[type][]interface{} or a map[type]map[uuid]interface{}. And that's somewhat naive as well. I'd probably implement a method to store and fetch each "type" that the ECS could actually care about, which could probably be

Re: [go-nuts] Noob question: Pointers to interfaces

Keep in mind: at this point, I'm only playing around with a Go implementation. What I'm trying to do is implement an Entity-Component-System. Each entity consists of a collection of components, each of which may have a different type. The first thing I'm trying to implement is an easy way to

Re: [go-nuts] Noob question: Pointers to interfaces

is this what you are looking for ? https://play.golang.org/p/_g2AbX0yHV see also the related so for what I fund interesting http://stackoverflow.com/questions/40060131/reflect-assign-a-pointer-struct-value On Tuesday, November 8, 2016 at 4:07:56 AM UTC+1, Kaylen Wheeler wrote: > > Here's what I

Re: [go-nuts] Noob question: Pointers to interfaces

Based on that example, I'm even more confused about what you are trying to accomplish. Can we take a step back and forget about the implementation of a solution and describe the problem you are working on? On Mon, Nov 7, 2016 at 19:08 Kaylen Wheeler wrote: > Here's what I have so far: https://pl

Re: [go-nuts] Noob question: Pointers to interfaces

Here's what I have so far: https://play.golang.org/p/X2z7Yl9UPg I think it works for my purposes. However, I'm confused about one thing: Why does reflect.Value.Set panic when passed a zero-value? On Monday, 7 November 2016 16:56:52 UTC-8, freeformz wrote: > > Then just use pointers (see lines

Re: [go-nuts] Noob question: Pointers to interfaces

I think that you want to write generic code in a language that doesn't have generics. Also, the description of the problem is incorrect. You describe how you want to solve the problem, my using pointers or changing the fields of structs, but you never describe the actual problem, how did you en

Re: [go-nuts] Noob question: Pointers to interfaces

I want pointers because I want most components to be structs, and I want the ability to modify the fields in those structs. On Monday, 7 November 2016 16:46:17 UTC-8, freeformz wrote: > > Why do you want to use pointers? > > On Mon, Nov 7, 2016 at 4:42 PM Kaylen Wheeler > wrote: > >> Thanks for

Re: [go-nuts] Noob question: Pointers to interfaces

Then just use pointers (see lines 45+): https://play.golang.org/p/vl47WDHOdN On Mon, Nov 7, 2016 at 4:50 PM Kaylen Wheeler wrote: I want pointers because I want most components to be structs, and I want the ability to modify the fields in those structs. On Monday, 7 November 2016 16:46:17 UTC-8

Re: [go-nuts] Noob question: Pointers to interfaces

Why do you want to use pointers? On Mon, Nov 7, 2016 at 4:42 PM Kaylen Wheeler wrote: > Thanks for the "basic pattern" example here. There's one little > modification I'm wondering about. > > Can this line: > > rv.Elem().Set(m[rv.Type()]) > > be changed to this? > > rv.Elem().Set(*&*m[rv.Type()

Re: [go-nuts] Noob question: Pointers to interfaces

This was also my swag at an example: https://play.golang.org/p/QG7g9veKEI PS: it's still not strictly "type safe". On Mon, Nov 7, 2016 at 4:46 PM Edward Muller wrote: > Why do you want to use pointers? > > On Mon, Nov 7, 2016 at 4:42 PM Kaylen Wheeler > wrote: > > Thanks for the "basic pattern

Re: [go-nuts] Noob question: Pointers to interfaces

Thanks for the "basic pattern" example here. There's one little modification I'm wondering about. Can this line: rv.Elem().Set(m[rv.Type()]) be changed to this? rv.Elem().Set(*&*m[rv.Type()]) If so, how can we check that the input value is a pointer to a pointer. Or alternatively, is it bet

Re: [go-nuts] Noob question: Pointers to interfaces

, 2016 at 4:30 PM To: golang-nuts Cc: , Subject: Re: [go-nuts] Noob question: Pointers to interfaces The point freeformz is making is that you loose compile time type safety. Your program can still be made type safe at runtime (i.e. not panic) but it's a cop out. Sometimes it is wor

Re: [go-nuts] Noob question: Pointers to interfaces

Ha ha ha! Thanks! -Original Message- From: Dan Kortschak Date: Monday, November 7, 2016 at 4:23 PM To: Michael Jones , Edward Muller , Kaylen Wheeler , golang-nuts Subject: Re: [go-nuts] Noob question: Pointers to interfaces Thank you Michael for that. I have written a small

Re: [go-nuts] Noob question: Pointers to interfaces

*> on behalf of Edward > Muller > > *Date: *Monday, November 7, 2016 at 4:05 PM > *To: *Kaylen Wheeler >, golang-nuts < > golan...@googlegroups.com > > *Subject: *Re: [go-nuts] Noob question: Pointers to interfaces > > > > FWIW: As soon as interface{} is in

Re: [go-nuts] Noob question: Pointers to interfaces

Thank you Michael for that. I have written a small package to help with this kind of uncertainty :) https://play.golang.org/p/vSnG-HGdrU On Mon, 2016-11-07 at 16:08 -0800, Michael Jones wrote: > Not precisely so…Interfaces, and type switches, and related > mechanisms are safe. Their type indeterm

Re: [go-nuts] Noob question: Pointers to interfaces

living concrete type of an expected type or else, like the cat, your program is dead. From: on behalf of Edward Muller Date: Monday, November 7, 2016 at 4:05 PM To: Kaylen Wheeler , golang-nuts Subject: Re: [go-nuts] Noob question: Pointers to interfaces FWIW: As soon as interface

Re: [go-nuts] Noob question: Pointers to interfaces

FWIW: As soon as interface{} is involved you are no longer "type safe". On Mon, Nov 7, 2016 at 2:56 PM Kaylen Wheeler wrote: > So, what I'm trying to accomplish is a little unusual, and may need some > explanation. > > Basically, I'm trying to find a typesafe way to access a type-indexed map > o

Re: [go-nuts] Noob question: Pointers to interfaces

On Monday, 7 November 2016 17:55:57 UTC-5, Kaylen Wheeler wrote: > > I'm trying to find a typesafe way to access a type-indexed map of > components. This map can contain objects of any type, and the keys are > reflect.Type. > > One strategy I thought may work would be to pass a pointer to a poin

Re: [go-nuts] Noob question: Pointers to interfaces

So, what I'm trying to accomplish is a little unusual, and may need some explanation. Basically, I'm trying to find a typesafe way to access a type-indexed map of components. This map can contain objects of any type, and the keys are reflect.Type. One strategy I thought may work would be to p

Re: [go-nuts] Noob question: Pointers to interfaces

The same explanation that applies to slices of interfaces (https://golang.org/doc/faq#convert_slice_of_interface ) applies to pointers to interfaces. You shouldn't need a pointer to interface anyway; what are you trying to do? > On Nov 7, 2

[go-nuts] Noob question: Pointers to interfaces

I'm new to Go, and I'm still trying to figure it out. I'm trying to write a function that takes a pointer to a pointer of any type. I tried writing it like this: type MyStruct struct { a int b int } func myFunc(p **interface{}) { fmt.Printf("Here is the type: %T\n", p) } func main() { v