tapirl

12 ms·

121.
by tapirl 2y ago
https://github.com/golang/go/issues/49085
122.
by tapirl 2y ago
It is a sad fact that Go is becoming more and more like JavaScript (and deviating from C).
123.
by tapirl 2y ago
Google even didn't consider supporting Go as an official flutter language.
124.
by tapirl 2y ago
The interning feature should be only used for some rare cases, it is not intended to be used widely.
125.
by tapirl 2y ago
Be aware that there is a bug in the current implementation (1.23.0 and 1.23.1) https://github.com/golang/go/issues/69370
126.
by tapirl 2y ago
First in the world? Or of Huawei?
127.
by tapirl 2y ago
AsciiDoc is a feature-rich markup language. It's great. But I have two complaints: 1. Its readability is not very good. There is too much non-content text for me. 2. The grammar set is not small and natural.
128.
by tapirl 2y ago
DON'T! Since Go 1.22, this way is highly not recommended. Please read * https://go101.org/blog/2024-03-01-for-loop-semantic-changes-... * https://go101.org/bugs/go-build-directive-not-work.htm
129.
by tapirl 2y ago
You are not familiar with Go.
130.
by tapirl 2y ago
If the "for ;;" loop semantics can be bolted on post-facto in a version update, nothing else couldn't. Go provides certain immutability.
131.
by tapirl 2y ago
Reasons are in the article. I'm not familiar with Python, so I don't understand what is the problem with Python. But I think the problem of Go is unrelated to Python.
132.
by tapirl 2y ago
> That's still among the strongest backwards compatibility guarantees in any major language. Not at all. See https://go101.org/blog/2024-03-01-for-loop-semantic-changes-... for reasons.
133.
by tapirl 2y ago
> Even in that case they did the behaviour change properly: Not in fact. Go core team has admitted that Go toolchain 1.22.n versions break backward compatibility: https://github.com/golang/go/issues/66092
134.
by tapirl 2y ago
GoTV does similar things but plays it explicitly: https://go101.org/apps-and-libs/gotv.html GoTV builds needed toolchain versions with the Go source code instead of downloading the pre-built toolchain packages.
135.
by tapirl 2y ago
What impact in your opinion?
136.
by tapirl 2y ago
2024: 17 new Rust game engines created, 3 new games made. :D
137.
by tapirl 2y ago
Which games are built with it mow?
138.
by tapirl 2y ago
It is possible to add more immutability in Go. There are many proposals for this: https://github.com/go101/go101/wiki/Go-immutable-value-propo... . The main reason nothing happened in this direction is the cor
139.
by tapirl 2y ago
I think it is best to let rsc answer your questions. :D
140.
by tapirl 2y ago
The tests are in the simplest forms, there are more complex use cases of traditional "for" loops. The complex cases are never explored by the authors of the change. And there are a large quantity of private Go code in the world.
141.
by tapirl 2y ago
:D It looks you don't understand the change at all. The statement "since Go 1.22, you should try to specify a Go language version for every Go source file" is made officially, not by me. > You have a well-documented histor
142.
by tapirl 2y ago
No convincing evidences to prove there are not such cases. In my honest opinion, if there are such cases in theory, there will be ones in practice. It is a bad expectation to hope such cases never happen in practice. The authors of the chan
143.
by tapirl 2y ago
Don't forget that the semantic change of traditional 3-clause "for" loops: https://go101.org/blog/2024-03-01-for-loop-semantic-changes-... Because of this change, Go 1.22 is actually the first Go version
144.
Go toolchain v1.22.n breaks Go 1 compatibility(go101.org)
1 points by tapirl 2y ago|0 comments
145.
by tapirl 2y ago
Is it possible to enhance channels to fit into the iterator need? I mean using them without always creating new goroutines.
146.
by tapirl 2y ago
> Channels require a different goroutine to send values while also receiving them ... The requirement is a limit of the current design and implementation. Channels can be enhanced to avoid the requirement.
147.
by tapirl 2y ago
`range aFunction` is kinda of new syntax, though I agree it is more a new semantic thing.
148.
by tapirl 2y ago
The idea listens promising. It is more intuitive than the current design.
149.
by tapirl 2y ago
That is why I say the two are not compatible.
150.
by tapirl 2y ago
What is meaningfulness of the two `yield` functions? I mean why not expand/inline them. To use channels as iterators efficiently, we need find a way to let the functions creating the channels return without creating new goroutines.

More ›