errcheck
CliWrap
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
errcheck
-
Linter to check for errors ignored with _
In our codebase I noticed a few cases where people ignored errors returned from functions by assigning them to _, ie result, _ := foo(). The errcheck linter doesn't seem to catch this, does anyone know of a linter that does?
-
Golang panics in libraries
And we also expect that the caller will check the error and handle it. There is a popular linter that checks it for us: errcheck.
-
Is it a bad convention to overwrite err variable?
You should be using golangci-lint, because all serious Go programmers should. golangci-lint contains errcheck, which will detect if you overwrite an error without having done something with it in the meantime. I consider this one of the most important linters (this doesn't just detect things that may sorta kinda someday turn into bugs, this quite likely is a bug RIGHT NOW), and it helps you have the confidence you can overwrite errors as you go and don't need to keep allocating new ones.
-
Integration Tests failing
Run golangci-lint over your code if you haven't already and pay special attention to errcheck's output.
-
Luciano Remes | Golang is πΌπ‘π’π€π¨π© Perfect
errcheck has a flag for that ;)
-
Proposal: Go 2: Lightweight anonymous function syntax
https://github.com/kisielk/errcheck, which is in most of the combined linter packages by default.
We'll agree to disagree about unused imports; imports have can side-effects.
-
Lies we tell ourselves to keep using Golang
I prefer functions returning errors over throwing exceptions. Whether it's Go's errors or ML-style options/results, they're both better than exceptions. I cannot remember the last time I had a bug from not checking an error in Go. There's also errcheck which I use as part of my linting that will catch unchecked errors, such that I cannot even commit the code.
-
I Want Off Mr. Golang's Wild Ride
> Go compiler raise an error if a variable (error) goes unused
It doesn't though. It's perfectly valid to not use the return value of a function that only returns an error, for instance.
There are static error checking tools you can use like https://github.com/kisielk/errcheck to work around this, but most people don't use them.
I've run into a lack of Go error checking many times. Many times it's just the trivial case, where the compiler doesn't warn about not checking the result of an error-returning function.
But often it'll be subtler, and the result of Go's API design. One example is its file writing API, which requires you to close the file and check its error to be correct. Many times people will just `defer file.Close()`, but that isn't good enough - you're ignoring the error there.
Worse still is e.g: writing to a file through a bufio.Writer. To be correct, you need to remember to flush the writer, check that error, then close the file and check that error. There's no type-level support to make sure you do that.
-
Trying Out Generics in Go
I'd be really happy with that! Building the functionality of errcheck[1] and ineffassign[2] into the compiler β or at the very least, into govet β would go a long way to allay my worries with Go.
I think the reason they don't do this is that it's a slight (albeit a very tiny one) against Go's philosophy of errors being values, just like any other. While the `error` type is standard and used throughout Go source code, it still just has a simple three-line definition[3] and is not treated as a special case anywhere else; there is nothing stopping you from returning your own error type if you wish. A third-party linter could simply check for the `error` type specifically, but the first-party tools should not, and there's nothing like Rust's `#[must_use]` attribute that could be used instead. I respect Go's philosophy, but I feel like pragmatism must win in this case.
[1]: https://github.com/kisielk/errcheck
CliWrap
-
ModularPipelines - Strong-Typed, Parallel, C# Pipelines - Would appreciate feedback and thoughts
That being said, keep up the good work. I see a lot of potential in combo with libs like https://github.com/Tyrrrz/CliWrap
-
Process Ids on C#
Check out CliWrap. https://github.com/Tyrrrz/CliWrap
-
A History of the FFmpeg Project
I am using CliWrap to create my own wrapper for the functionality I need from FFmpeg. Works pretty well!
https://github.com/Tyrrrz/CliWrap
-
Creating a service that runs other executables (Windows Server)
Take a look at https://github.com/Tyrrrz/CliWrap for calling another process from one process.
- Calling PowerShell Azure module and creating resource group from C#
-
Why do Task.Wait and Task.Result even exist?
For example, using the great Cli.Wrap library:
-
Add persisted parameters to CLI applications in .NET
We can use Verify to perform snapshot testing and check for the correct output of the program. In order to make things easier and simplify working with process output capturing and invocation, I used CliWrap.
- GUI for a command line program
-
I Want Off Mr. Golang's Wild Ride
> You can take a look at System.Diagnostics.Process for one of the worst offenders.
Yeah, this is one of my least favourite APIs in all of .NET. My understanding is that the .NET team is planning to redo it in the next few years, but if you want something better right now I highly recommend the excellent CliWrap library: https://github.com/Tyrrrz/CliWrap
-
A 3 minute video on how to use PowerShell directly in C#
I religiously use CliWrap which makes things a bit easier, but still issues on some things like Async Processes and the start thing i spoke about
What are some alternatives?
GoLint - [mirror] This is a linter for Go source code. (deprecated)
Sieve - βοΈ Clean & extensible Sorting, Filtering, and Pagination for ASP.NET Core
staticcheck
Command Line Parser - The best C# command line parser that brings standardized *nix getopt style, for .NET. Includes F# support
gosimple
Fluent Command Line Parser - A simple, strongly typed .NET C# command line parser library using a fluent easy to use interface
gcvis - Visualise Go program GC trace data in real time
spectre.console - A .NET library that makes it easier to create beautiful console applications.
apicompat - apicompat checks recent changes to a Go project for backwards incompatible changes
CsConsoleFormat - .NET C# library for advanced formatting of console output [Apache]
Go Metalinter
SharpNetSH - A simple netsh library for C#