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
This style seems a net positive to me in many circumstances, but specifically for records I see it mostly as a downgrade (unnecessary indentation and code churn), and I'd like to propose to special-case it.
This is similar in style to #1545/#1634, but for a completely different part of the syntax, so I figured it should be filed separately.
The text was updated successfully, but these errors were encountered:
This would inevitably land in a discussion of where should the exceptions apply; for simplicity I'd propose only bare records (typedef Foo = (...);) and nullable records (typedef Foo = (...)?;), regardless of whether they contain positional or keyword fields. A record wrapped in another type of (e.g. typedef Foo = FutureOr<(...)>;) would be unchanged from the current tall-style.
The new formatter (#1253) changed the formatting of record
typedef
s, adding quite a bit of indentation:Old formatter:
New formatter:
This style seems a net positive to me in many circumstances, but specifically for records I see it mostly as a downgrade (unnecessary indentation and code churn), and I'd like to propose to special-case it.
This is similar in style to #1545/#1634, but for a completely different part of the syntax, so I figured it should be filed separately.
The text was updated successfully, but these errors were encountered: