You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I like most hlint's suggestions, I really don't like the suggestion of turning:
function (Ctor (Rec { field })) =...-- into:
function (CtorRec { field }) =...
or likewise
function (A { a }) (B { b }) =...-- into:
function A { a } B { b } =...
I find the latter versions harder to read because I think of unparenthesized whitespaces as separating function arguments which is not the case with the named field puns syntax.
Unfortunately, I feel like my options are either to turn off all redundant bracket warnings, or live with it.
Would it be conceivable/reasonable to split the redundant brackets into some sub-categories?
The text was updated successfully, but these errors were encountered:
I think it would be quite reasonable to pretend that you do need a bracket in this case - and I thought we even did in the past. So make remove redundant bracket not warn in this case.
While I like most hlint's suggestions, I really don't like the suggestion of turning:
or likewise
I find the latter versions harder to read because I think of unparenthesized whitespaces as separating function arguments which is not the case with the named field puns syntax.
Unfortunately, I feel like my options are either to turn off all redundant bracket warnings, or live with it.
Would it be conceivable/reasonable to split the redundant brackets into some sub-categories?
The text was updated successfully, but these errors were encountered: