Getting excited for Go 1.18's lesser known features

• go

  2,067 119,397 10.0 Go

  The Go programming language

  

I think its important to understand that big parts of the software community over-rely on this type of programming. In my opinion, over use of higher order functions is a cancer on programming languages, and should be used at the absolute minimum, or even omitted from a language entirely.

https://github.com/golang/go/issues/45955#issuecomment-83235...

• versioninfo

  6 231 3.7 Go

  Importable package that parses version info from debug.ReadBuildInfo().

I subscribed to GH activity for the correspondence friendliness-enhancing library by the author:

https://github.com/carlmjohnson/versioninfo/

The primary motivation curiousity to learn if this becomes "the [best/default] way" folks reach for when leveraging BuildInfo to deliver explicit binary versioning.

• InfluxDB

  www.influxdata.com sponsored

  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.

  

• wuffs

  80 3,736 9.4 C

  Wrangling Untrusted File Formats Safely

  

agree -- ultra useful alternative to splitting

would be neat to imagine a language where this was an optimizer feature rather than a decision the programmer made. many functions that return an array are ultimately using just one, or a few elements of it. the compiler can make a lot of decisions in the caller about how to reduce allocation or short-circuit array processing.

I think, but am not sure, this is what the experimental parsing language 'wuffs' is about https://github.com/google/wuffs -- the language itself is aware of array lengths as a first-class citizen and can make decisions accordingly

Suggest a related project