Abhinav Gupta

Mock: Fix AfterFunc data race

1

There's a data race if we call Mock.AfterFunc and Mock.Add concurrently. The included test demonstrates this with `go test -race`. ``` $ go test -race ================== WARNING: DATA RACE Read...

Add a minimal GitHub Workflow configuration for CI on the project. This will test against both currently supported versions of Go per the [Go Compatibility Guarantee](https://golang.org/doc/go1compat).

Atomic updates

3

Currently, if a rebase fails after a few branches have been updated, you're left in an inconsistent state where half the branches have been updated and the other ones are...

Announcement: Archival imminent

1

This is just a notice that we'll be archiving this repository in a week. If you're an active user, we encourage you to fork the project or use Buf. Thanks!

`[...]` in function calls should match any and all generic function instantiations. ```diff @@ @@ -foo[...](42) +bar[...](42) ``` Should match: ``` foo(42) foo[int](42) foo[MyInt](42) ```

Understand decl groupings

4

For gopatch, currently the following are different: ``` var foo = 42 var ( foo = 42 ) ``` gopatch should understand decl groupings for types, consts, vars, and funcs...

We should support metavariables to match on literals. That is, to match on `"foo"` and `42` below. ``` x := "foo" const y = 42 ``` This will make it...

It's currently impossible to have a patch that introduces a new top-level declaration while modifying another one. For example, given, ``` func foo() { re := regexp.MustCompile("foo") // ... }...

We should support a `-d` flag to print the diff of what would be changed without changing anything. If the diff was non-empty, the program would exit with a non-zero...

We should support a `-l` flag to list matches of a patch without changing anything. This could be used to implement simple linters.