This blog post is extremely interesting. I wish I have better background in type theory and in complexity theory, I would understand this text much better.
Due to my work (C#, C++, and some trivial stuff) I have almost no time to follow development of Go, so I have question about "There are also still discussions about changing the generics design.". Is changing a design of generic still possible without breaking backward comparability? As I said, I have a little time for Go now (thought luck), so this question maybe just show how ignorant I'm. "As one example, the limitations we introduced to fix all of this made one of the use cases from the design doc impossible to express." Time before release of Go 1.18 was the last moment, when I have more time for Go and in beta version some examples from "Type Parameters Proposal" (https://go.googlesource.com/proposal/+/refs/heads/master/design/43651-type-parameters.md) refereed here already wasn't working. Ian Lance Taylor said that current descriptions of generics is to be found appropriate version of Go Spec and maybe latter "Type Parameters Proposal" would be updated. So I want to ask, is this example from "Type Parameters Proposal" relevant today? I mean July 2022. Few pedantic questions and comments. I always find things to gripe about. Like my English level. In the section "SAT" we have definition of function func F(x, y, z bool) bool but in the example just below we call function f(true, true, false) Starting from the the section "Basic interfaces as type sets" we have type X interface { X() } type NotX interface{ X() int } and it is quite consistent that interface X has "interface { X() }" and NotX has "interface{ X() int }" (there is no space just after "interface"). Is this by design or by accident? In section "Adding unions" we have type S interface{ I believe lack of space after "interface" is just mistake. Best regards, Kamil wtorek, 17 maja 2022 o 14:01:31 UTC+2 axel.wa...@googlemail.com napisał(a): > On Tue, May 17, 2022 at 11:44 AM Peter Galbavy <pe...@wonderland.org> > wrote: > >> I am neither enough of a Go expert ("yet) - I hope) or good enough in >> real math to say much apart from that is actually one of the clearest >> explanations of P/NP problems and the actual meaning of CNF/DNF that I have >> had the pleasure to read. Even setting aside the importance to the design >> decisions for Go 1.18, it actually made sense of things I have struggled in >> the past to "get".\ > > > Thanks for the kind words :) I've heard this a couple of times by now and > while I'm a bit surprised (it doesn't seem a very novel way to describe it > to me, but then again, I'm biased) I'm very happy that I apparently hit > home with this :) > > >> >> Thanks. >> >> On Monday, 16 May 2022 at 11:24:22 UTC+1 axel.wa...@googlemail.com wrote: >> >>> Hi, >>> >>> I thought you might be interested in a new blog post I just published, >>> about the difficulties of proving that a type set is empty: >>> https://blog.merovius.de/posts/2022-05-16-calculating-type-sets/ >>> It is based on a problem that came up when the notion of type sets was >>> proposed >>> <https://github.com/golang/go/issues/45346#issuecomment-813639125>. It >>> came up a couple of times lately in discussions about changing the generics >>> design, so I thought it might be good to do a clean writeup. >>> >>> Let me know what you think. >>> >> -- >> 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...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/a2dd523a-56c4-4bfb-99e2-7245a708a578n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/golang-nuts/a2dd523a-56c4-4bfb-99e2-7245a708a578n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/9399a4ba-4a7c-45f7-a7fd-2a3bc1a260acn%40googlegroups.com.
