Matt Sherman
Matt Sherman
I don’t know a good way to do this (have wanted for myself too). Aliasing is the “supported” way – gen’s supported use case is for local (package) types only....
@artwyman Thanks for using `gen`! It does parse [multiple type parameters](https://github.com/clipperhouse/typewriter/blob/master/lex.go#L205), and they are [exposed on TagValue](https://github.com/clipperhouse/typewriter/blob/master/tag.go#L10). Yeah, my biggest blocker for primitive types is the notation — there is...
Hmm, sounds like not a great idea. gen is for _your_ types -- I assume that the generated proto files represent an external package's types?
Fair, though I don't have a good suggestion off the top of my head. Show me some sample code?
I'll have too look into this, having not used CGO myself.
Hi Dragos! No, gen doesn't do reflection at all, so it won't give you a reflect.Type. On Dec 1, 2016 9:10 AM, "Dragos Bulugean" wrote: > Hi @clipperhouse ! >...
Not quite sure I follow (I haven't used BoltDB) but perhaps you are describing something analogous to an ORM? I think it would work for that. gen is about writing...
It’s designed to generate one file per-type-per-typewriter. I think that’s a decent way to do it. How many types are you working with here?
I’m not set on it. It’s a good default, but very much a matter of taste. Some config might be a solution. Sounds like you want to mark up all...
Sure, will think about it. I’m sure that as others work on typewriters, they’ll want some control over that.