4 ms·
We use this library at work and although keeping up with the constant API changes is annoying, it works well. My main complaint is that this library is very "un
by grose 11y ago
We use this library at work and although keeping up with the constant API changes is annoying, it works well. My main complaint is that this library is very "un-Go". Everything is a pointer, even required parameters. I understand that this is a result of automatic code generation used meet the needs of various APIs with different semantics, but Go's lack of pointer literals makes it hard to use (you can't write something like &"hello world"). So I consider this a low-level library, and wrap it with more Go-friendly code.
The devs are definitely aware of this issue, and I thank them for getting rid of map pointers. I don't think there's an easy solution.
- goddardcm 11y agoWorth noting that they provide helpful functions for pointer-ization: https://github.com/aws/aws-sdk-go/blob/master/aws/types.go https://github.com/aws/aws-sdk-go/blob/master/aws/types.go