3 ms·
Out of curiosity, what resources were you not finding? The language itself and the standard libraries are pretty well documented on golang.org, and searching fo
by supersillyus 16y ago
Out of curiosity, what resources were you not finding? The language itself and the standard libraries are pretty well documented on golang.org, and searching for "golang <keyword>" has always worked quite well for me to find any third party library I happen to be looking for.
- jbooth 16y agoI'm working on a wrapper for BLAS (basic linear algebra subprograms) that will hopefully be able to interoperate between CBLAS and CUBLAS (nvidia's GPU implementation) by the time it's done. BLAS has fortran/C heritage so it expects matrixes to be a single contiguous chunk of memory, indexed by column first and then row. Whereas a go [][]float64 is a pointer to an array of slices, which are pointers to noncontiguous arrays. Additionally, the CUDA API has a "special" malloc function that does some bookkeeping and gets big performance gains. So, trying to figure all of that out, plus this is my first go project (great first project, huh), so basically every other newbie question I've had. Basically obscure enough questions were better to search golang-nuts directly.
- lukesandberg 16y agoi've definetly had the same problem googleing for go resources. i also eventually figured out that doing a search for golang <whatever> was the best way to go. still it can be kind of frustrating for a beginner with the language to always get the query wrong the first time. luckily the documentation and source code available on golang.org is really useful.