Alonely0 🦀

@recursive_recursion @snaggen It’s just a glorified text editor, if it gets too bad it’s not like your hands are tied.

@snaggen the actual answer is having opt-out semver checks on cargo publish just like with git.

@soulsource @anlumo dude your whole code is UB. A reference & means that the data behind it never changes while any reference exists, allowing multiple pointers to point at it at the same time (aliasing); whereas a mutable reference &mut means that the data behind may only be read or written by that pointer, i.e. multiple pointers (aliasing) can’t exist. The compiler uses this to optimize code and remove stuff that you promise never happens. Always use miri, and go read the nomicon.

@MakeAvoy @snaggen Have you ever written a recursive macro with multiple variadic arguments, my friend? It is so cursed, yet so good when it works (if it works).

@mmstick @Ogeon Have you looked into the algorithm Google uses for material you on Android? You could use it to do the same in Cosmic.

@ron Too many linked lists is one of my favorites https://rust-unofficial.github.io/too-many-lists/

@Arbitrary I did this a while ago, you might find it useful. It abandons the more traditional vector concept of sequential insert, so that remove() can be implemented. https://github.com/Alonely0/Lariv

@livingcoder @snaggen Yep, I proposed it because I was tired of recording (neo)vim macros for that. I can’t recall who implemented it but they made it surprisingly quickly, and looks like it works well.