Our great sponsors
-
-
Nim
Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
vscode-gremlins
Gremlins tracker for Visual Studio Code: reveals invisible whitespace and other annoying characters
-
zio-prelude
A lightweight, distinctly Scala take on functional abstractions, with tight ZIO integration
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Does anyone know the impetus for using [] in generics? I know Nim opted for the same syntax and I assume it has some parsing/tokenizing benefit like the switch to using “fn” a la Zig or Rust. However, the syntax seems needlessly ambiguous with array notation sharing the same operator. I know I’m not alone because I’ve seen others mirror my concerns in Nim.
[0] https://github.com/nim-lang/Nim/issues/3502
> Was the try() proposal for Go error handling?
Yes, it was the second proposal by the Go team for shorter error handling: https://github.com/golang/proposal/blob/master/design/32437-...
> I'm really curious what happened to the proposals for shorter Go error handling
The community didn't like it and it was declined:
On VSCode, I use the Gremlins extension which highlight all those suspicious characters.
https://github.com/nhoizey/vscode-gremlins
