miniblog.

Should code completion offer private methods/fields? If the user chooses a private method, you can offer a quickfix to change its visibility. It's clutter though. I frequently find myself wanting fields that I haven't exposed yet, and frustrated that the IDE hides them.

Is there a good canonical name for autofixes, where a static analysis tool can apply a change to resolve an issue? Clang calls them fix-its, LSP calls them quickfixes.

I'm experimenting with diagnostics formatting. * I've added a left margin, showing both the file name and line numbers * I'm showing one line of context above/below the offending line. * I'm using grey for comments. What do you think? Is there anything you'd change?