Swift Task Naming API #2619
Swift Task Naming API #2619
Conversation
Harjas12
force-pushed
the
task-naming-api-proposal
branch
2 times, most recently
from
7f71aac to
c0e0748
Compare
proposals/0454-task-naming-api.md
Outdated
|
|
||
| ```swift | ||
| init( | ||
| name: String? = nil, |
There was a problem hiding this comment.
-- no change after all here --
There was a problem hiding this comment.
If I may ask: is something you both would consider for the naming API to use an enum? I am asking this, because it would be also good to in case of having to iterate over the Tasks we may have, comparing them or even making using a switch. Of course, my suggestion is not to remove the String as a type for naming it, but having a second flexible way to deal with them.
What do you think?
There was a problem hiding this comment.
Proposal "content" discussions let's do in the review thread on the Swift forums
|
@Harjas12 I did some updates, please check and merge them :) |
Harjas12
force-pushed
the
task-naming-api-proposal
branch
from
d1443e9 to
205a51e
Compare
rjmccall
added
the
LSG
|
This is now implemented and we could kick off a review -- swiftlang/swift#79600 The proposal is up to date. cc @swiftlang/language-steering-group |
No description provided.