smartstring
ixy-languages
smartstring | ixy-languages | |
---|---|---|
7 | 30 | |
482 | 2,108 | |
- | 0.0% | |
0.0 | 0.0 | |
8 months ago | over 1 year ago | |
Rust | TeX | |
Mozilla Public License 2.0 | BSD 2-clause "Simplified" License |
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.
smartstring
-
Does using "String" instead of "&str" a lot results in unoptimised code?
Your use case sounds like it will involve a lot of small strings that use a subset of UTF-8. If you’re concerned about performance, you could look into something like smartstring. Sixbit also looks interesting, but it looks like it won’t give you any more characters and it’d probably require additional computation to do the conversion (and they’d have to be converted back out).
-
Rust Is Hard, Or: The Misery of Mainstream Programming
> If you have a long-running async function, then pass parameters by value! If you have a polymorphic async function, then return your result in a Box.
I've taken to making heavy use of the smallvec and smartstring crates for this. Most lists and strings are small in practice. Using smallvec / smartstring lets you keep most clone() calls allocation-free. This in turn lets you use owned objects, which are easier to reason about - for you and the borrow checker. And you keep a lot of the performance of just passing around references.
I tried to use async rust a couple of years ago, and fell on my face in the process. Most of my rust at the moment is designed to compile to wasm - and then I'm leaning on nodejs for networking and IO. Writing async networked code is oh so much easier to reason about in javascript. When GAT, TAIT and some other language features to fix async land I'll muster up the courage to make another attempt. But rust's progress at fixing these problems feels painfully slow.
https://crates.io/crates/smallvec / https://crates.io/crates/smartstring
-
GitHub - epage/string-benchmarks-rs: Comparison of Rust string types
Just to point out, smartstring no longer assumes String memory layout. From the changelog:
-
Why is str not just [char]?
There's some really good crates that implement SSO floating around - eg, SmartString. But I agree - its a pity they're needed. Swift built this into the core string type in the language. I think that was the right call.
-
Announcing `compact_str`! A super memory efficient immutable string that is transparently stored on the stack, when possible
Comparatively: * SmolStr can inline up to 22 bytes but does not adjust down for 32-bit architectures, meaning it's potentially wasting memory on 32-bit archs. Similarly though it's immutable and Clone is O(1) * SmartString can inline up to 23 bytes, but it's mutable and Clone is O(n). Also this crate makes assumptions about the memory layout of a String, which in theory should be fine, but is a slight caveat.
-
Version 0.19.15 released.
SmartString is used to store identifiers (which tends to be short, fewer than 23 characters, and ASCII-based) because they can usually be stored inline. Map keys now also use SmartString.
-
Speed of Rust vs. C
I’ve been using smartstrings, which is both excellent and maintained. https://github.com/bodil/smartstring
ixy-languages
-
The Garbage Collection Handbook, 2nd Edition
Not really, here it is winning hands down over Swift's ARC implementation.
https://github.com/ixy-languages/ixy-languages
- rust devs in a nutshell
-
So what you doing for the weeknd
You laugh, but ... https://github.com/ixy-languages/ixy-languages
-
Blog post: My perspective on RAII and memory management in C++ and Rust
GC'd languages are designed to leverage GCs, meaning they usually allocate a lot. Some of the more recent ones (C#, Go) have ways around it or to limit it, but in your average GC'd language you have to really bend yourself out of shape to limit allocations (IIRC the Ixy effort / study / thing never managed to make the Java hotpath allocation-free).
- “Rust is safe” is not some kind of absolute guarantee of code safety
-
I wrote a database engine in Typescript
It's kind of funny when you see things like this project: https://github.com/ixy-languages/ixy-languages
-
What are my prospects in web programming, if I don't like JS?
like not-even-in-the-same-ballpark faster. In this realworld example (userspace network drivers in managed languages) JS manages about 20-30% of native code performance, python iirc is below 1%
-
Don’t call it a comeback: Why Java is still champ
- Support for generic-aware value types (struct vs. class) and low-level features like stackalloc: very valuable for high-performance scenarios and native FFI. See for instance https://github.com/ixy-languages/ixy-languages. In comparison, Java doesn't even have unsigned integers. Yes, Project Valhalla is coming someday.
As well, debatable to some folks, but: properties (get/set); operator overloading; LINQ > Java streams; extension methods; default parameters; collection initializers; tuples; nullable reference types; a dozen smaller features
- Reference Count, Don't Garbage Collect
-
Why did you switch from another language to Rust? Do you regret not learning it earlier?
Very bottom of this file https://github.com/ixy-languages/ixy-languages/blob/master/Java-garbage-collectors.md
What are some alternatives?
smol_str
ctl - The C Template Library
compact_str - A memory efficient string type that can store up to 24* bytes on the stack
cats - Lightweight, modular, and extensible library for functional programming.
min-sized-rust - 🦀 How to minimize Rust binary size 📦
redgrep - ♥ Janusz Brzozowski
libskry_r - Lucky imaging library
c-examples - Example C code
bitter - Extract bits from a byte slice
iced_audio - An extension to the Iced GUI library with useful widgets for audio applications
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.