Rust Paste

In Rust the thing you most often want to show someone is the error, and rustc errors are gloriously verbose: a borrow-checker complaint spans many lines with --> source pointers, ^^^^ underlines, note: and help: blocks, and carefully aligned carets that only make sense if the alignment survives. Paste that into Slack and the carets drift off the tokens they point at, turning a precise diagnostic into noise. files.link renders Rust through highlight.js and stores the text verbatim, so a pasted compiler error keeps its source pointers and underlines lined up, and source snippets keep their structure.

That's the core angle here: a Rust paste is frequently a *diagnostic*, not just code. When you ask for help with a lifetime error or a trait-resolution failure, the help comes from the reader being able to read rustc's own annotations exactly as you saw them. Pick Rust for source, or plain text when the output is mostly the error formatting — either way the error[E0499]: ... headers, the spans, and the suggested fixes stay aligned and copyable.

For source, the gnarly Rust constructs that chat tools mangle all render cleanly: explicit lifetimes (<'a>), impl Trait and dyn Trait, where clauses, async/.await, pattern matches with guards, and macros — both macro_rules! definitions and call sites like println!, vec!, and derive attributes. files.link doesn't compile anything; when you need to actually build or run, the Rust Playground is the tool, and a paste is for sharing the source or the error it produced.

If you'd rather hand over a full file or crate artifact than a snippet, host it as a file instead of pasting it.

No signup to create or read. Anonymous pastes hold 100KB and expire after 24 hours — enough for almost any error dump. Sign in for 1MB and any expiry up to permanent, useful for a minimal reproduction you'll attach to a GitHub issue or a forum thread that should still resolve later. A Gist needs a login to publish; a Slack block won't open for someone outside your team. A paste link opens for anyone and, critically for rustc output, keeps the alignment.