Ah yeah didn't notice the others got named that way without the selector
after perform. Yeah it seems like it was simply mismapped. I suggest
filling a radar about ASAP (not in the standard library realm).
On Tue, Aug 16, 2016 at 8:52 AM Philippe Hausler wrote:
> I would claim that perhaps it sho
I would claim that perhaps it should be:
open func perform(inBackground aSelector: Selector, with anArgument: Any?)
That way it matches the completion family of the rest of performing. But if
that is the case we should take a look at the onMainThread ones as well so they
look like this perhaps:
It is following the naming methodology of a sentence like structure
"performed selector in background with ". It does read a
little strange but likely comes from a simple remapping of the existing
objective-c name for familiarly reasons.
It could be performInBackground(selector:,with:) ... "Perfo
> On Aug 16, 2016, at 8:42 AM, Philippe Hausler via swift-corelibs-dev
> wrote:
>
> Those methods should probably all belong to the same family of `perform` but
> it matches the method naming of:
>
> open func performSelector(onMainThread aSelector: Selector, with arg: Any?,
> waitUntilDone
Those methods should probably all belong to the same family of `perform` but it
matches the method naming of:
open func performSelector(onMainThread aSelector: Selector, with arg: Any?,
waitUntilDone wait: Bool, modes array: [String]?)
But perhaps the naming family should belong to this one:
o
Hello!
I just noticed that performSelectorInBackground(_:withObject:) has
been mapped to performSelector(inBackground:with:) in Swift 3. So:
performSelector(inBackground: #selector(doStuff), with: nil)
This seems confusing to me – the "inBackground" label has little to do
with the selector that
