i use Aves Libre from FDroid. it has an editor with simple drawing.
undefined
gram
@orsinium@fosstodon.org
Post
-
@eclectechi use Aves Libre from FDroid. -
Everything is beautiful in #golang:"Arrays have their place, but they’re a bit inflexible, so you don’t see them too often in Go code."What for and why they designed Array then?#scentmark[4]int is on stack, *[4]int is on heap. slices are powered by *[N]T arrays.
using arrays directly is rare, that's the point. however, having them in the language is essential for the language to work.
-
Everything is beautiful in #golang:"Arrays have their place, but they’re a bit inflexible, so you don’t see them too often in Go code."What for and why they designed Array then?#scentmarka point in 3D space would be a struct{x, y, z int} but a vector in 100-dimension space would be [100]int.
-
Everything is beautiful in #golang:"Arrays have their place, but they’re a bit inflexible, so you don’t see them too often in Go code."What for and why they designed Array then?#scentmark1. arrays are allocated on stack, not heap. slices cannot be allocated on stack because their size is not statically known.
2. array size is static and part of the type. taking a[4] from 2-element array is compilation error.
3. a[0] on array usually produces faster and safer code because boundary check is static.
4. arrays power slices.
use arrays when all items are the same type and their number is known. you'll know when you can. for example, matrices in a 3D game engine.