What problem are you trying to solve?
Unify the usage of space after the // single-line comment start and the actual text.
I prefer there's a space. IMHO this is the industry standard. While some code doesn't use it.
If it was up to me, I'd implement the recipe as enforcing a single space.
But I can imagine someone'd call for it to be configurable.
Describe the situation before applying the recipe
//Find the first partition with a recipe run
...
// Link to the commit trace if it exists
...
Describe the situation after applying the recipe
// Find the first partition with a recipe run
...
// Link to the commit trace if it exists
...
Any additional context
Watch out, there might be some conventions or not-for-human comments which might actually require no space, e.g.
What problem are you trying to solve?
Unify the usage of space after the
//single-line comment start and the actual text.I prefer there's a space. IMHO this is the industry standard. While some code doesn't use it.
If it was up to me, I'd implement the recipe as enforcing a single space.
But I can imagine someone'd call for it to be configurable.
Describe the situation before applying the recipe
Describe the situation after applying the recipe
Any additional context
Watch out, there might be some conventions or not-for-human comments which might actually require no space, e.g.