From 0dff66f45391eee730efedc8f4ef3d2dd4cd7742 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=9D=8E=E6=99=93=E8=BE=89?= Date: Fri, 20 Dec 2019 15:43:35 +0800 Subject: [PATCH] Updated Go2GenericsFeedback (markdown) --- Go2GenericsFeedback.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Go2GenericsFeedback.md b/Go2GenericsFeedback.md index 39eaceb8..f3176981 100644 --- a/Go2GenericsFeedback.md +++ b/Go2GenericsFeedback.md @@ -352,4 +352,6 @@ func main() { - antoniomo: While the draft clearly explains why `F`, `F[T]` and non-ASCII (unable to type it here) `F<>` where discarded, feels like `F{T}` would be more human readable than the sometimes three in a row set of `()`, while not complicating the parser with unbounded lookahead as you can't open a block in those circumstances. -- aprice2704: I really dislike the idea of using regular parentheses `(`, would a two-character sequence cause compiler overhead from unbounded lookahead? How about <| and |> ? would they work? They have the advantages of being quite distinct from `(`, making some visual sense in ascii, and in the 'Fira Code' font (highly recommended) which I use in VSCode there are ligatures to render these as little right or left pointing triangles. \ No newline at end of file +- aprice2704: I really dislike the idea of using regular parentheses `(`, would a two-character sequence cause compiler overhead from unbounded lookahead? How about <| and |> ? would they work? They have the advantages of being quite distinct from `(`, making some visual sense in ascii, and in the 'Fira Code' font (highly recommended) which I use in VSCode there are ligatures to render these as little right or left pointing triangles. + +- leaxoy: First I'm sorry for editing the page footer, however I can't remove footer content. This is my opinion: lots of `(` & `)` made go looks so messy, `<` & `>` like other language is better, and is more kindly for those come from other languages. \ No newline at end of file