Hey Doug,
How do I use it in Swift code without a wrapper, which is understandably a bit
pointless, if I still support iOS 9?
Sent from my iPhone
> On 5 Sep 2016, at 05:05, Brandon Knope via swift-evolution
> wrote:
>
> Where should the lack of {public} be reported then?
>
> This seems like
Where should the lack of {public} be reported then?
This seems like it falls under jira and not radar because it's in swift open
source but I'm not 100 percent
Brandon
Sent from my iPad
> On Sep 4, 2016, at 11:48 PM, Douglas Gregor wrote:
>
>
>
> Sent from my iPhone
>
>> On Sep 3, 2016,
Sent from my iPhone
> On Sep 3, 2016, at 11:32 AM, Ben Rimmington via swift-evolution
> wrote:
>
>
>> On 3 Sep 2016, at 19:13, Brandon Knope wrote:
>>
>> Thank you! I was looking for this last night and failed.
>>
>> Why do you think {public} isn't included?
>
> I don't know, but trying
The context of comments should clearly not be ignored by IDEs. If you did that,
the entire feature set of doc comments would go away.
-David
Sent from my iPhone
> On Sep 4, 2016, at 5:15 PM, Félix Cloutier via swift-evolution
> wrote:
>
> There is a *lot* more to `#pragma` than `#pragma mar
There is a *lot* more to `#pragma` than `#pragma mark`, but it's unclear to me
what other pragma anyone would bring over from C. Given that, I'm not in favor
of a new language construct for just one thing that's not horribly out of place
as a comment.
Félix
> Le 4 sept. 2016 à 15:53:46, isidor
Hi all,
I think the "old style" `#pragma` is necessary in Swift.
Exactly in the same way it is available in C/C++ or Objective-C/C++, or in
something else portable way.
Because `#pragma` is not handled in Swift, in Xcode they overloaded the
semantic of comments, giving to the comment `// MARK:
> On Sep 4, 2016, at 10:28, Fayez Hellani via swift-evolution
> wrote:
>
> Hey! There should be an option to name variables AND constants dynamically.
> For e.g. in an app from storing recipes, where the user creates a recipe,the
> recipe should be stored in a constant (as a structure) with a
Have you thought about using a dictionary? You can fetch a recipe by looking up
a key:
let foods: [String: Foods] = [:] // fill it up appropriately with your own data
let recipe = foods[TitleTextField.text].recipe
Saagar Jha
> On Sep 4, 2016, at 10:28, Fayez Hellani via swift-evolution
> wr
Hey! There should be an option to name variables AND constants dynamically. For
e.g. in an app from storing recipes, where the user creates a recipe,the recipe
should be stored in a constant (as a structure) with a name
“\(TitleTextField.text)_Recipe” (e.g. “Lasagna_Recipe”), so that it gets sto
+1
I like this especially considering that 64 bit iOS has led to more boxing
to `NSNumber` for convenience
On Fri, Sep 2, 2016 at 1:23 PM, Scott James Remnant via swift-evolution <
swift-evolution@swift.org> wrote:
> 👍
>
> Makes ObjC APIs even easier to work with, without any cost to working with
10 matches
Mail list logo
