Elias Gabriel Amaral da Silva

Is this just Hyrum's Law, or does Postgres actually guarantees an order for `returning` queries?

Yes right now I am using offsets.. I get the offsets with [`Parser::into_offset_iter`](https://docs.rs/pulldown-cmark/latest/pulldown_cmark/struct.Parser.html#method.into_offset_iter) and then I can use [String::replace_range](https://doc.rust-lang.org/std/string/struct.String.html#method.replace_range) in the original string. That way I guarantee that I am...

Ok so, I was thinking about this and I think that the signature of your [`cmark_resume_with_source_range_and_options`](https://docs.rs/pulldown-cmark-to-cmark/latest/pulldown_cmark_to_cmark/fn.cmark_resume_with_source_range_and_options.html) basically has all information needed to work losslessly. So you don't need a new...

There is also [simple_mermaid](https://docs.rs/simple-mermaid/latest/simple_mermaid/) and some other mermaid-related crates, but as far as I can tell they also just uses the the mermaid js library underneath and don't attempt to...

Could this be added into the workspace's `Cargo.toml` rather than `.cargo/config.toml`? Or is this intended to be applied to all workspaces inside a directory?