-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Don't deprecate splat #48038
Don't deprecate splat #48038
Conversation
The standard way we do backports (changes that should be made to a version which has already had its feature freeze) is merging a PR to master and tagging it with the appropriate backport label (in this case This has been somewhat controversial, so I'm tagging this and #47714 (the issue with most of the discussion on the topic) with the triage label so folks will discuss it on a video call. You are welcome to join! See the #triage slack channel for logistical info. |
@LilithHafner OK sorry and thanks for the correction. Should I split this into a main PR on master, and a small one on |
The backports will have their news aggregated with their version bump, if I recall correctly, so just a PR targeting master should be enough. |
7623da0
to
6259887
Compare
Keep the splat function and mention in the documentation that it's the recommended way of constructing a Base.Splat object.
6259887
to
ee64566
Compare
I've updated the PR to target master. I dropped the change to |
Ah, you're referring to |
Yes exactly (I should have said that more clearly). |
Triage approves |
Keep the splat function and mention in the documentation that it's the recommended way of constructing a Base.Splat object. (cherry picked from commit 670190c)
As discussed in #47714, this keeps the functionality introduced in #42717 but using the existing
splat
API, exportingsplat
instead ofSplat
.This targets the release-1.9 branch since there are modifications to the 1.9 version ofNEWS.md
.