Open belkadan opened 5 years ago
Part of rdar://problem/47493396. I think this is StarterBug-able: find all the places where we're using the getObjectTypeAndOptionality
helper and see which ones are places where we could print the nullability separately using NullabilityPrintKind::ContextSensitive
.
hi @belkadan, I would like to take this one, can I assign it to myself? 🙂
Go for it! Feel free to comment here if you have questions, or open a partial PR even if you don't have it fully working.
@adellibovi, still working on this one?
(I'm checking in on all the StarterBugs that haven't been touched in over a month; it's totally fine if you just haven't had time but still want to keep it.)
Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | Compiler | |Labels | Improvement, PrintAsObjC, StarterBug | |Assignee | @adellibovi | |Priority | Medium | md5: 0bc925759fd7590c0a91c67c7a5de68fIssue Description:
Objective-C supports two "pretty" forms for nullability qualifiers: within the parentheses of a method's parameters or return type:
And in the property attributes list for a property:
PrintAsObjC should adopt these where valid; right now it only uses them in hardcoded cases for
instancetype
.