Barbucca
Barbucca is a genus of loaches native to Southeast Asia. It is currently the only genus in its family.[1][2]
Barbucca | |
---|---|
Scientific classification | |
Kingdom: | Animalia |
Phylum: | Chordata |
Class: | Actinopterygii |
Order: | Cypriniformes |
Superfamily: | Cobitoidea |
Family: | Barbuccidae Kottelat, 2012 |
Genus: | Barbucca T. R. Roberts, 1989 |
Type species | |
Barbucca diabolica T. R. Roberts, 1989 |
Species
There are currently two recognized species in this genus:[3][4]
- Barbucca diabolica T. R. Roberts, 1989
- Barbucca elongata Vasil'eva & Vasil'ev, 2013[4]
gollark: Well, yes, but they're byte sequences.
gollark: I mean, it's better than C and stuff, and I wouldn't mind writing simple apps in it.
gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.
References
- Froese, Rainer, and Daniel Pauly, eds. (2013). "Barbuccidae" in FishBase. April 2013 version.
- Kottelat, M. (2012): Conspectus cobitidum: an inventory of the loaches of the world (Teleostei: Cypriniformes: Cobitoidei). Archived February 11, 2013, at the Wayback Machine The Raffles Bulletin of Zoology, Suppl. No. 26: 1-199.
- Froese, Rainer and Pauly, Daniel, eds. (2013). Species of Barbucca in FishBase. April 2013 version.
- Vasil'eva, E.D. & Vasil'ev, V.P. (2013): ДВА НОВЫХ ВИДА КАРПООБРАЗНЫХ РЫБ ИЗ ФАУНЫ ОСТРОВА ФУКУОК, СИАМСКИЙ ЗАЛИВ, ВЬЕТНАМ. Voprosy ikhtiologii, 53 (3): 269-277.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.