Unordered function parameters (and Python **kwargs)

[xAlien95 (Stefano De Carolis)]

@Lantua

Maybe we can do something like this?

struct PlotProperties { ... }
func foo(properties: PlotProperties) { ... }

foo(properties: .init(thickness: 30, ...))

I'm afraid that using a separate structure for properties could make things worse for the end user. But thank you for the suggestion, that's a pattern that in a way I used frequently in JavaScript, since there aren't named parameters. I feel I may stick with either a long initializer or forcing the user to set the properties after the plot initialization.

---

@cukr

I would love to implement the autocompletion you're suggesting, but SwiftCompletion.cpp looks complicated, and I am unable to compile swift on either linux or macos :(

@Lantua

That's why it'd be nice if I can see which argument is defaulted w/o relying on the documentation.

I feel like autocompletion issues should eventually be discussed/proposed in a separate and more focused thread to gain the right audience. Code completion is even explicitly stated in the Swift 6 road map:

There are major investments currently underway to improve the core developer experience, such as:

• Faster builds
• More informative and accurate diagnostics
• Responsive code completion
• Reliable and fluid debugging experience

And many others.