Fantastic work! I'm no authority on the subject of Go programming style but the CheckErrors and OK pattern seems very unusual. Can you tell me the reasons for that design choice?
On Tuesday, 19 September 2023 at 10:13:54 pm UTC+10 Pascal Costanza wrote: > Hi, > > > I am happy to announce a library that we have been working on at Intel. > > It is a Go binding for the GraphBLAS <https://graphblas.org> C API that > calls into the widely used SuiteSparse:GraphBLAS C library. > > > You can find the Go binding at forGraphBLASGo > <https://github.com/intel/forGraphBLASGo/> and some example algorithms at > forLAGraphGo <https://github.com/intel/forLAGraphGo>. > > > GraphBLAS is a specification for an API that defines standard building > blocks for expressing graph algorithms in the language of linear algebra. > It consists of data types for opaque representations of sparse matrices, > vectors and scalars over the usual elementary types (Booloans, integers, > floating point numbers), as well as user-defined element types. Operations > on those data types include matrix-vector, vector-matrix, matrix-matrix > multiplications, element-wise addition and multiplication, and so on. Apart > from the usual integer and floating point addition and multiplication, > client programs can use other arbitrary operators with these high-level > operations, represented as monoids or semirings, to express a wide range of > powerful algorithms. > > > SuiteSparse:GraphBLAS is a complete implementation of GraphBLAS in the C > programming language. It is used heavily in production. For example, it is > used as the underlying graph engine in FalkorDB (previously RedisGraph), > and as the built-in sparse matrix multiply in MATLAB. Several bindings > exist for SuiteSparse:GraphBLAS for Python, Julia, and PostgreSQL. > > > The forGraphBLASGo library is a binding that defines a Go API for > GraphBLAS and the SuiteSparse:GraphBLAS extensions. It strives to adhere to > Go programming style as much as possible. Most prominently, it uses type > parameters that have been introduced in Go 1.18 to make the various > GraphBLAS object types generic, for added type safety. Other supported Go > features include: using multiple return values instead of reference > parameters, and Go-style error handling. > > > We consider the forGraphBLASGo library as quite mature. However, we > haven’t yet assigned the version number 1.0.0 to it yet. If you have any > feedback or suggestions for improvement, please let us know. > > > The forLAGraphGo library is less mature and still work in progress. > > Looking forward to hearing what you think about this library. > > > Thanks a lot, > > Pascal > > -- 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/731a3bf6-a4af-408d-9e4c-20d781bf73e0n%40googlegroups.com.
