Robert Griesemer
Robert Griesemer
For basic types Go already has special syntax for their values: We can write numbers (incl. `0`) for numeric types, strings (incl. `""`) for string types, `true` and `false` for...
[edited: added missing keys in struct literal] Presumably one could write: ```Go var s struct{x int; y float32} = struct{...}{x: 1, y: 2} ``` and the `2` in the struct...
I'd think that returns work like assignments (of the result values to the result variables) and thus should behave the same way with respect to evaluation order. (Haven't investigated the...
I'm sympathetic to the general idea, but I find the specific examples given not very convincing: The relatively small savings in terms of syntax doesn't seem worth the trouble. But...
In Go, the syntax for function declarations deviates a bit from the regular pattern that we have for other declarations. For constants, types, variables we always have: ``` keyword name...
@dimitropoulos I've been working on V8 alright, but that was building the virtual machine, which was written in C++. My experience with actual Javascript is limited. That said, Javascript is...
@neild Apologies for being imprecise: What I meant this sentence is that if there were new different syntax (arrows or what have you), it should be somewhat regular and apply...
@mknyszek I will take this on.
#65711 has been fixed and is unrelated to this issue.
This is clearly a bug in the implementation. Cycles are poorly defined in the spec. Not sure we can fix this for 1.23, but probably not a release blocker because...