Felix Hildén

The concern raised about commented code goes the other way too. If we have a line that is just under the limit, and is then commented, bringing it over the...

I'm becoming slightly in favor of having this as an opt-in. Either that, or not at all. We could start by just splitting lines that *only* have comments, to get...

Thanks for the submission! But I don't think this is good in general, meaning in all cases with a comment line between arguments. Also, I think this could be extended...

That's fair, but in that case a comment can help. Black won't analyse the list and determine that "A-ha, the list of strings ends there and afterwards there are only...

Oh, a bit negligent of me. That *is* the special case. And I see your point: particularly before comments, the newlines can indeed improve readability. Consider me slightly swayed, and...

Hi! Tell me if I'm off base here, but isn't that essentially solved by our line length parameter? If we wanted to break only four letters after 88, we could...

That probably is it, thanks! So I'll respond to that. And to clarify, we're only considering cases where the final formatting still breaks line length limits, right? To entertain the...

A list of modules or prefixes for inventory items could work. So specifying `library.foo` would disable inventory warnings for either just that entry or alternatively everything under it.

As per #97, I think the configuration name will be `codeautolink_warn_on_unassigned_name`, *if* we decide to do this. This would require us to change our parsing logic a bit. It's not...

The subscripts might also be slices, so we definitely need a way to recognise them or ignore cases that are too complex.