News for hackers. Stuff that matters.
Re:A Go contract design combining the strong points of offic... by hacknat on Saturday November 16, 2019 @03:19PM (#21554705)
That’s a lot of new, effectively, keywords that you’re introducing. I don’t know if that’s a bad or a good thing, but I suspect the community will have a hard time with it. Otherwise this is a creative solution.
Re:A Go contract design combining the strong points of offic... by mbnull on Saturday November 16, 2019 @03:58PM (#21554907)
It uses effectively only the one keyword assure. The constraints look like fields on the type variables, which have an ambiguity with package private method expressions with the same name.
Re:A Go contract design combining the strong points of offic... by dotaheor on Sunday November 17, 2019 @12:11PM (#21558797)
The constraint expressions are expected to be used in generic declaration body scopes instead of top package scopes. For example: https://github.com/dotaheor/unify-Go-builtin-and-custom-gene..., so I think the ambiguity should not happen.
Re:A Go contract design combining the strong points of offic... by karmakaze on Monday November 18, 2019 @09:44PM (#21570280)
I would prefer naming that feels less procedural. I think of it like a guard so maybe `when` or `where`. It can also just be some punctuation like `| cond` `| another-cond`.