RVS_Generic_Swift_Toolbox
ego
RVS_Generic_Swift_Toolbox | ego | |
---|---|---|
3 | 1 | |
6 | 56 | |
- | - | |
4.4 | 4.0 | |
4 months ago | 4 months ago | |
Swift | OCaml | |
MIT License | GNU General Public License v3.0 only |
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.
RVS_Generic_Swift_Toolbox
-
Internationalization best practices for front-end developers
[0] https://github.com/RiftValleySoftware/RVS_Generic_Swift_Tool...
[1] https://github.com/RiftValleySoftware/RVS_Generic_Swift_Tool...
[2] https://github.com/RiftValleySoftware/RVS_Generic_Swift_Tool...
[3] https://developer.apple.com/library/archive/documentation/Co...
-
Ask HN: What are some 'cool' but obscure data structures you know about?
Ole Begemann and Chris Eidhoff wrote Advanced Swift, and, in there, described a really efficient FIFO queue.
I implemented a variant ofit, in my Generic Swift Toolbox Package[0]. It’s lightning fast.
[0] https://github.com/RiftValleySoftware/RVS_Generic_Swift_Tool...
-
Swift Playgrounds 4
Found it, but it's not what I need.
I need a target to be a playground; not a project.
The idea is to be able to assign resources, files, and SPM modules to a playground, so they are available to the code running in the playground (an example might be an SPM module like my Generic Swift Toolbox Module[0]). I can then work with the code I'm prototyping in a lightweight text file.
[0] https://github.com/RiftValleySoftware/RVS_Generic_Swift_Tool...
ego
-
Ask HN: What are some 'cool' but obscure data structures you know about?
Shameless plug, I also maintain an OCaml implementation of egraphs (named ego) at https://github.com/verse-lab/ego
While the most popular implementation at the moment seems to be egg in Rust, I find that OCaml serves as a much more ergonomic environment for quickly prototyping out uses of egraphs in practice. As a bonus, ego also shares the same logical interface as egg itself, so once you've finalised your designs, you shouldn't have much trouble porting them to egg if you need the performance gains.
What are some alternatives?
plurid-data-structures-typescript - Utility Data Structures Implemented in TypeScript
PSI - Private Set Intersection Cardinality protocol based on ECDH and Bloom Filters
dictomaton - Finite state dictionaries in Java
sdsl-lite - Succinct Data Structure Library 2.0
pvfmm - A parallel kernel-independent FMM library for particle and volume potentials
us - An alternative interface to Sia
swift - the multiparty transport protocol (aka "TCP with swarming" or "BitTorrent at the transport layer")
Folly - An open-source C++ library developed and used at Facebook.
hamt - A hash array-mapped trie implementation in C
multiversion-concurrency-control - Implementation of multiversion concurrency control, Raft, Left Right concurrency Hashmaps and a multi consumer multi producer Ringbuffer, concurrent and parallel load-balanced loops, parallel actors implementation in Main.java, Actor2.java and a parallel interpreter
gring - Golang circular linked list with array backend
FusionCache - FusionCache is an easy to use, fast and robust cache with advanced resiliency features and an optional distributed 2nd level.