TokenPress

With every strip flag off, Python formatting is context-lossless: comments, docstrings and annotations are kept, and only syntactic noise (whitespace, blank lines, indentation width) is minimized.

In the browser, verification is internal only (re-parse plus canonical re-emit equivalence): WebAssembly cannot spawn processes, so the command-line tool's --verify external, which runs tsc --noEmit or node --check over the output, is not available here.

With that flag off, Go formatting is context-lossless: every comment survives byte for byte — trailing and inline ones included — and only whitespace is minimized. With it on, the comments the Go toolchain reads as instructions are still kept: //go: directives, /*line*/ and build constraints (//go:build and the legacy // +build). At either setting a file that imports "C" is left byte for byte identical, so a cgo file reports no savings at all.

In the browser, verification is internal only (re-parse plus AST equivalence): WebAssembly cannot spawn processes, so the command-line tool's --verify external, which runs gofmt -e over the output, is not available here.

With that flag off, Java formatting is context-lossless: every comment survives byte for byte — Javadoc, trailing and inline ones included — and only whitespace is minimized. With it on there is no keep-list: javac reads nothing out of a comment, so unlike Go there are no directives to preserve and the Javadoc of a stripped file goes with the rest of its comments. At either setting a file whose comments carry a \uXXXX escape that could decode into a comment marker is left byte for byte identical — javac decodes those escapes before lexing and the grammar does not — so such a file reports no savings at all.

In the browser, verification is internal only (re-parse plus AST equivalence): WebAssembly cannot spawn processes, so the command-line tool's --verify external, which runs javac over the output, is not available here.

With that flag off, C# formatting is context-lossless: every comment survives byte for byte — /// XML documentation, trailing and inline ones included — and only whitespace is minimized. With it on there is no keep-list, and C# has one more thing to lose than Java: the grammar gives //, block comments and /// a single node kind, so an XML documentation comment cannot be told apart from an ordinary one by kind and the API documentation of a stripped file goes with the rest of its comments. At either setting a file where the grammar and a real compiler could disagree about where a comment ends — a comment crossing an #if/#endif pair, one carrying a line terminator the grammar does not honour (U+0085, U+2028, U+2029), or one shielding a preprocessor directive from the start of its line — is left byte for byte identical, so it reports no savings at all.

In the browser, verification is internal only (re-parse plus AST equivalence): WebAssembly cannot spawn processes, so the command-line tool's --verify external, which compares the diagnostics Roslyn's csc reports before and after, is not available here.