buffet VS stan

Made this C lib for exactly the reasons you mention. I love C but got mad at the constant bounds errors and copying.

https://github.com/alcover/buffet

Dynamic allocation, SSO, views, refcounting, etc.. are spread on various implementations.

C++ separates string and string_view. And they're not fully compatible. (Ex. you can't concat cross-type !?).

Rust has str, &str, String Box, ... ?

In the spirit of "a slice of a string is still a string", why not pack it all into a single type ? And offer security in the process.

Here's the scheme : https://github.com/alcover/buffet/raw/main/assets/schema.png

Here's the code : https://github.com/alcover/buffet

Buffet

Buffet – An All-inclusive Buffer for C\ (63 comments)

Buffet

That sounds very interesting. Maybe it would not be very hard to implement a prototype of such a system with Stan?

Would you be okay if we add Soisy to the list of companies using stan?

However, I'm a huge fan of static tools like this in general. I've heard great things about https://package.elm-lang.org/packages/jfmengels/elm-review/latest/ and I need to try out https://github.com/kowainik/stan. Also its possible HLint has ways to write more advanced rules and I just don't know about them, but even if that's so hopefully I've explained why just dropping it in isn't a huge win.