Scott Meeuwsen

No issue pulling this in, but for some weird reason my code coverage run is now saying this reduces it by 50% - obviously not true, but will have to...

I played with a box but couldn't find a reason to add it. Allocation seemed about the same (I may need to revisit and check again in light of your...

I also should add you can do this on your own. This was my example in the "make your own string" section. If you can give me a use case...

So your use case is that you've found `Box` to allocate faster than `Arc`? Just want to understand the driver.

The biggest issue I'm having is one of identity. Right now `LocalStr` and `SharedStr` are a pair and I plan to release optimizations to go back and forth. If I...

FlexStr 0.8.0 had alignment issues due to the enum. That made it's performance inconsistent. Mostly it seems in inline strings but I can't seem to nail it down. 0.9.x doesn't...

I appreciate that. I'm interested in getting use and willing to do the work, so let me know what you need. I argue because I want to understand the 'why'....

I would be interested to hear how you used it. In my benchmarks `Arc` and `Rc` are slightly slower than `String` on allocation (like 5-10% tops) and are much faster...

Fair points - really it is as easy as me adding this: ```rust type BoxStr = FlexStrBase; ```

I'm not sure I understand. `LocalStr` and `SharedStr` are literally copying the `&'static str` ref on clone so it should be approx. the same speed as copying the ref itself...