aboriginal
Aboriginal Generics: the future is here! (by vasilevp)
fut
By cretz
aboriginal | fut | |
---|---|---|
6 | 2 | |
169 | 0 | |
- | - | |
10.0 | 0.0 | |
over 4 years ago | over 2 years ago | |
Go | Go | |
MIT License | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
aboriginal
Posts with mentions or reviews of aboriginal.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-29.
- Golang Aboriginal Generics (2019)
-
so that one can write f <o> g. Yes, user-defined operator <o> in C++ ;-) Note that I used the LaTeX symbol "circ" and it's visual look o. You can use this trick for any named operator.
Glad to see the c++ community finally embracing the spirit of true innovation. Perhaps Canadian Aboriginal syllabics are soon within our grasp
-
Imagine someone is paying you to destroy their codebase. How would you do it?
This is awesome, reminds me of this: https://github.com/vasilevp/aboriginal
-
I once called a variable with a reserved word "lambda" because it would look nice with other variables "alpha", "beta". I did it by replacing the last a with Russian a
I think this calls for a revisiting the Aboriginal Generics for Gophers
- Trying Out Generics in Go
-
Trojan Source: Invisible Vulnerabilities - Abusing Unicode RTL and BiDi References to hide source code in your source code
This is my favorite.
fut
Posts with mentions or reviews of fut.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-22.
-
Go Generics Facilitators
Undocumented early impl/design of futures: https://github.com/cretz/fut
-
Trying Out Generics in Go
I feel the similar way, though I wouldn't be so brave to say I didn't ever use interface{}. I think we all work around slices and maps being the only generic containers and don't know we do. I think everyone will find that while they didn't need generics, they will help them when using utility libraries. Java 1.4 people thought the same.
I expect a well-curated libraries to come about that will really simplify some otherwise difficult problems for people (e.g. task/object pooling). I'm even toying with a futures impl at https://github.com/cretz/fut, but I wouldn't use it in place of channels in most cases.
What are some alternatives?
When comparing aboriginal and fut you can also consider the following projects:
trojan-source - Trojan Source: Invisible Vulnerabilities
ineffassign - Detect ineffectual assignments in Go code.
errcheck - errcheck checks that you checked errors.
functools - Functional tools in Go 1.18 using newly introduced generics
gods - Go Data Structures
gostdx - Extended library functions using generics in Go.
reason - Simple, fast & type safe code that leverages the JavaScript & OCaml ecosystems
go - The Go programming language