Search Results for "compiler"

...We encourage you to get started with Go and Gonum if you are tired of sluggish performance, and fighting C and vectorization, and also if you are struggling with managing programs as they grow larger. Get Gonum if you want code to be fully transparent, and want the ability to read the source code you use. It is useful if you’d like a compiler to catch mistakes early, but hate fighting linker and unintelligible compile errors.

Samber/lo is a Lodash-style Go library based on Go 1.18+ Generics. This project started as an experiment with the new generics implementation. It may look like Lodash in some aspects. I used to code with the fantastic "go-funk" package, but "go-funk" uses reflection and therefore is not typesafe. As expected, benchmarks demonstrate that generics are much faster than implementations based on the "reflect" package. Benchmarks also show similar performance gains compared to pure for loops. In...

Go is a compiled language, but with very fast compilation, that allows one to use it in a REPL (Read-Eval-Print-Loop) fashion, by inserting a "Compile" step in the middle of the loop -- so it's a Read-Compile-Run-Print-Loop — while still feeling very interactive. GoNB leverages that compilation speed to implement a full-featured (at least it's getting there) Jupyter notebook kernel. As a side benefit it works with packages that use CGO — although it won't parse C code in the cells, so it...

...It normalizes their results into one consistent output format so editors, IDEs, and CI systems can read problems more easily. The tool helps developers catch issues such as unused code, unchecked errors, duplicated code, style problems, security concerns, and suspicious compiler-level behavior. It supports a broad collection of linters and lets users customize which checks run for each project. It can also be configured through a JSON file, which makes it easier to share linting rules across a team. Although the project is archived and users are directed toward golangci-lint, it remains a useful example of early Go lint aggregation.