Deprecate the Indexable protocols #4091
Conversation
Using them is always a mistake; the user should choose the corresponding Collection protocol instead.
|
@swift-ci Please test and merge |
1 similar comment
|
@swift-ci Please test and merge |
|
@swift-ci Please test Linux platform |
|
Drive-by rebuild. @swift-ci please test Linux platform. |
|
It keeps timing out?! @swift-ci Please test Linux platform |
It's important to let people know that, in contrast with existing practice in other frameworks, we really are going to remove the deprecated API, and soon.
|
@swift-ci Please test and merge |
|
It keeps timing out?! @swift-ci Please test Linux platform |
|
@swift-ci Please test and merge |
|
Would |
|
@jrose-apple Actually you have to choose between renamed and a message. The compiler will eat it, but will only give you one. |
|
@swift-ci Please smoke test |
|
Hm, okay. We definitely do both for unavailable, but maybe the diagnostic was getting too complicated for deprecated. |
|
It turns out this commit was the cause of the timeouts—the parse_stdlib_*.sil tests are choking for whatever reason. Investigating. |
|
…okay, -parse-sil really shouldn't emit availability warnings. That's all it is. |
[pull] swiftwasm from main
These should really never be used except by the standard library