gotgo

I also miss generics in Go. It is especially a pain to implement a nice high performance collections library without them. I have been working on and off on a data-structures library and you have to go through a lot of hoops to make it nicely usable and your still end up with `interface{}` everywhere.[1] It should be noted that this is not the first attempt by any means. droundy implemented basically this several years ago.[2] The problem is these things are non-standard and I don't feel comfortable using them. I want generics but I want them as part of the language not as some weird third party CGI script. I also want them integrated into the template system. That way I can create type variables which must implement an interface. However, when the code is actually run, it isn't an interface object it is the actual object. Features like t

Since Go can do generics via code generation [1], I'm not convinced that it can't also do ORM via code generation. OTOH, I'm not particular fond of ORM as a universally right solution for dealing with DBs (its a solution which makes sense for some DB-related issues in some OO languages, but isn't something that should be reflexive "deal with DB, need ORM"), and its probably not a solution I would reach for for any problem in Go even whether or not you could reasonable do it in Go. [1] https://github.com/droundy/gotgo

This looks similar to an older generics system for Go, `got` (GO Templates). Got was pretty cool, but Go 1.0 broke it due to the parser getting stricter. Edit: found it: https://github.com/droundy/gotgo

A Go templating project was posted here the other day: gotgo[0]. I haven't had a chance to use it yet, but it may alleviate some small amount of pain. As for poor performance, that is almost certainly a result of rampant object creation, rather than reuse. Not sure how much of his program was concurrent, how sophisticated it was, etc. Ultimately if the data set fit in memory, Python would probably be the appropriate choice for this kind of computation. [0] https://github.com/droundy/gotgo

> So far despite all the people lamenting the lack of generics in Go I've yet to have seen someone propose a viable (eg: backwards compatible, realistic to achieve with the current compilers and runtime, etc.) way to implement, nevermind someone who's produced a prototype. https://github.com/droundy/gotgo

FYI https://github.com/droundy/gotgo

> I really want to like Go, but I'm having a hard time believing that they don't have a plan for generics. I've read the FAQs about go+generics, but do we have any better idea of when generics might make an appearance? As a language feature: not likely any sooner than Go 2.0, given everything that's been said on the issue, though I suppose if a way could be found to do generics that doesn't explode compilation time and doesn't involve syntax changes that would break any existing Go 1.x code, it might happen in a later 1.x release. Wouldn't hold my breath. Via a preprocessor? Its already a thing: https://github.com/droundy/gotgo

Someone's already provided a template processor for/in Go that provides generics. https://github.com/droundy/gotgo

> The generic, functional map function cannot be written, and never will. https://github.com/droundy/gotgo/blob/master/example/slice.g...

I really love go, I try to use it whenever I can. That being said, I still have the feeling that having to rewrite a lot of dummy boilerplate code because of lack of generic collections hinders my productivity. I completely understand that introducing that in the language it's a pandora box, etc etc (not only because of compiler's complexity and compilation speed). But still, I have to find a way around that, being DRY has obvious advantages (although depending too much on obscure magic can be a problem); it's not just a random language feature from my favorite language. I'm trying to see whether https://github.com/droundy/gotgo helps

Here's one https://github.com/droundy/gotgo

Well actually, people with bizarre build requirements are starting to use clean Go source code as a build target of their increasingly diverse preprocessors. Can't be healthy. [1]: https://groups.google.com/d/msg/golang-nuts/LQMv7Zsmsi0/8Aax... [2]: https://github.com/jteeuwen/go-bindata [3]: http://stackoverflow.com/questions/9838304/resource-bundling... [4]: https://github.com/chanwit/kgc [5]: https://github.com/droundy/gotgo