optparse
fst
Our great sponsors
optparse | fst | |
---|---|---|
5 | 11 | |
314 | 1,709 | |
- | - | |
0.0 | 3.5 | |
6 months ago | 3 months ago | |
C | Rust | |
The Unlicense | The Unlicense |
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.
optparse
-
Porting my very simple C code from Unixen/macOS to Windows
Between -std=c99 and removing these headers, you're missing time definitions (struct timeval, gettimeofday) and option parsing definitions (struct option, getopt_long). Mingw-w64 provides all this for compatibility, but MSVC has none of these, so you'll need to write replacements. I've written embeddable, public domain implementations of getopt and something like getopt_long, in case that helps. These are how I deal with option parsing portability.
-
How to properly handle position non-specific program arguments? ./my_prog --format:"mp3"
getopt_long is a GNU extension, common across unix-like systems, for parsing long options. You can find libraries for functionality as well.
-
How to make programs for linux
When I need something more sophisticated, where long options would be nice, I reach for my own Optparse.
-
[ Feed back wanted ] Is this a good way to handle lot of if instead of if else?
https://github.com/skeeto/optparse (short and long)
-
Debian discusses vendoring again
This is bug-free and feature complete so it never needs to be updated. When I need argument parsing in a C program, I just copy-paste that into my source and massage it into place. Sometimes I cut the fprintf() stuff, or replace the isalnum, or otherwise adapt it to fit the program's needs. The point is that it becomes wholly owned by the project using it. It's a similar story for long option parsing.
fst
- fst: Represent large sets and maps compactly with finite state transducers
-
Creating a perfect HashMap from string keys known in advance
I'd point you towards BurntSushi's fst crate: https://github.com/BurntSushi/fst
-
How to use mmap safely in Rust?
The fst crate effectively relies on mmap for it to work right. The folks here suggesting you just use the heap might be right, but only if using the heap is actually plausible. If your dictionary is GBs big (an FST might be bigger than available memory), then copying it the heap first would be disastrous.
-
Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.64]
You'll love what we're working on if you're interested in the implementation of:- Tantivy- Meilisearch- Finite State Transducers
-
rustc is unacceptably slow compiling long lists of constant slices
Here's an example of longest prefix matching using a FST which I based my approach on: https://github.com/BurntSushi/fst/pull/104/files
-
Official /r/rust "Who's Hiring" thread for job-seekers and job-offerers [Rust 1.63]
Finite State Transducers
-
Wikit Desktop - A dictionary application using tauri GUI framework
As a result, I have a plan to implement a desktop version from then and I finished today with a beta version. The desktop is based on tauri, and the dictionary index algorithm is FST (it is an awesome index algorithm).
-
WordBueno.com online dictionary. Fast, no frills, mobile friendly.
WordBueno’s data is currently derived from Wiktionary. The backend is using Rust’s warp with fst for indexing.
- Show HN: WordBueno: sleek dictionary built with Rust and Svelte
-
Speed of Rust vs. C
No you don't. I've written multiple programs that load things instantly off the file system via memory maps. See the fst crate[1], for example, which is designed to work with memory maps.
Rust "works badly with memory mapped files" doesn't mean, "Rust can't use memory mapped files." It means, "it is difficult to reconcile Rust's safety story with memory maps." ripgrep for example uses memory maps because they are faster sometimes, and its safety contract[2] is a bit strained. But it works.
[1] - https://github.com/BurntSushi/fst/
[2] - https://docs.rs/grep-searcher/0.1.7/grep_searcher/struct.Mma...
What are some alternatives?
getopt - POSIX getopt() as a portable header library
smartstring - Compact inlined strings for Rust.
perl5 - 🐪 The Perl programming language
rust-fnv - Fowler–Noll–Vo hash function
itoa - Fast function for printing integer primitives to a decimal string
itoa - Fast integer to ascii / integer to string conversion
redgrep - ♥ Janusz Brzozowski
wingetopt - getopt library for Windows compilers
libskry_r - Lucky imaging library
tao - The TAO of cross-platform windowing. A library in Rust built for Tauri.