I propose to add synaptic sugar for creating pointers. This involves use of the
Swift provides a handy way to create optionals. This involves the use of
T? rather then
Optional<T> However, when creating pointers, things can be especially verbose.
There should be syntactic sugar for an
T is from the declaration
Similar to optionals, this should not affect readability because it is unlikely that you will have many
*s. At most you will have 2 if you want to split text by some delimiter.