3 ms·
Why not fork?
by k__ 10y ago
Why not fork?
- geodel 10y agoyes, why not?
- monsieurbanana 10y agoYou really think a fork will help here? Can you explain a bit more how do you think a fork will work out?
- k__ 10y agoSo one side has its Go with generics and one without and in the end we would see which would do better?
- tapirl 10y agowhy not both?
- rdtsc 10y agoGo++ should at least be an April 1st thing, since it is coming up.
- josefx 10y agoIt should add everything C++ has or would that go2far ?
- pjmlp 10y agoBecause everyone of us that cares about generics uses languages that support them, and most likely a Go++ effort would be in vain, after all there are already a few Go preprocessors, which don't seem to be widely adopted.
- k__ 10y agoAlso, are generics really the only way to go? I mean, parametric polymorphism is achievable with different approaches...
- bluejekyll 10y agoAnd maintain type safety?
- vetinari 10y agoMaybe algebraic data types would be more suitable. In Go, you don't have subclassing, so you cannot implement YourClass<T extends SomeAncestor>.
- stymaar 10y ago> Maybe algebraic data types would be more suitable. There is no opposition between ADT and generics. In fact most language that have ADT have generics… > In Go, you don't have subclassing, so you cannot implement YourClass<T extends SomeAncestor>. There is no link between generics and inheritence, functionnal languages usually don't have OOP mechanism but they still have generics.
- deleted 10y ago[deleted]
- zeveb 10y agoTake a look at CLOS. It's for a dynamically-typed language, but the same principles could be used to provide for multi-methods in a statically-type language like Go.
- coldtea 10y agoBecause I don't have Google's money to support it.
- camus2 10y agoWith what money and whom to maintain the fork? The survey even shows that most go users never or rarely contribute the any open source go project (25% + 34% respectively). You'd need a solid corporate backing.
- zzzcpan 10y agoWhy fork? To depend on Go? Compile into Go instead.
- majewsky 10y agoI have repeatedly thought about building a variant of Go that compiles down to Go and then gets compiled by the upstream compiler, mostly to add generics and autogenerate all these if err != nil { return nil, err } blocks. But it would most definitely be a pain in the ass to integrate this with the toolchain.