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 is technically a duplicate of #4146, however, that issue had a subtly massive scope since it covered both chains and calls (similar to #4306) and I was thinking about extracting a new issue focused on the call args piece.
Is your interest strictly in a compressed-like variant on calls, or would it be alright with you if we broaden this a tad to discuss the feasibility of a new option to cover call layout/style (naming will be fun given the unfortunate name of the existing option that actually controls params in fn items, not args in calls), with Compressed being a potential variant?
I suspect some of the original challenges (#2010) that prevented a compressed variant in the first place are still prevalent, but I wonder if some form of a preserve-variant similar to what we're targeting for chains could be possible as a middle ground.
I just have these occasional FFI calls which have to match a particular many-args signature and rustfmt makes them take up half a page of space.
I have no opinions on if chains should be in scope or how they should work if they are. I just need normal function calls to work. That's the only time I'm stuck with this many args instead of combining them into an array or a args-struct or a builder or something else like that.
Just how fn_args_layout works for function declarations, but make it work for function calls as well.
eg:
should become (depending on line with and such) something like this:
instead of going to a completely vertical layout.
The text was updated successfully, but these errors were encountered: