Post

Replies

Boosts

Views

Activity

Comment on Why doesn’t getAPI() show up in autocomplete despite having a default implementation in a protocol extension?
@DTS Engineer Thank you for answering my question 😆 I expect it to autocomplete as getAPI() when I press the return key in the state shown in the screenshot you provided. However, it always autocompletes as getAPI(from: <#String?#>). The same behavior occurs even in a new project. If I modify the existing code to the following and execute it, the autocomplete should behave the same. However, I’m not sure what difference is causing it not to work: i think
Topic: Programming Languages SubTopic: Swift Tags:
Jan ’25
Comment on Why doesn’t getAPI() show up in autocomplete despite having a default implementation in a protocol extension?
@DTS Engineer Thank you so much! 👏 I submitted the feedback as you suggested (FB16403003). I hope the suggestion gets accepted and implemented soon. Personally, I believe this would greatly enhance the developer experience, especially for those developing SDKs. 🤞
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Jan ’25
Comment on Why doesn’t getAPI() show up in autocomplete despite having a default implementation in a protocol extension?
@DTS Engineer Thank you for answering my question 😆 I expect it to autocomplete as getAPI() when I press the return key in the state shown in the screenshot you provided. However, it always autocompletes as getAPI(from: <#String?#>). The same behavior occurs even in a new project. If I modify the existing code to the following and execute it, the autocomplete should behave the same. However, I’m not sure what difference is causing it not to work: i think
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Jan ’25