a quick first lock looks promising to me: I like the blog post, as it does IMHO a gentle introduction to your angle of attack. Having used mocking (or one of its twins/cousins/... for those who insist on this not being mocking, alas) on Python I've up to now found the Go mock packages to be difficult and with rather unwelcoming documentation. As for the naming: kudos for naming it what it is, clear and concise, imagination be reserved to where it applies, not just here. On Monday, January 8, 2024 at 3:39:31 AM UTC+1 Corin Lawson wrote:
> I recently published a blog post about Go generics. I've found that > there's lots of very good technical information about generics in Go, but I > felt that they are lacking some gritty experience reports. > > > https://medium.com/versent-tech-blog/go-generics-tips-tricks-and-pitfalls-4342b82f9eeb > > The blog also introduces a new approach to generating mock objects in Go. > > https://github.com/Versent/go-mock > > I'm seeking feedback (as an inexperienced blogger) and also thoughts on > the mock lib (apologies for the lack of naming creativity), > > Thanks for your time. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/9b791784-cb6d-4bbb-af67-3489701a4f84n%40googlegroups.com.
