Rob Amos

It looks to be the ordering of the call to `-[UITableView moveRowAtIndexPath:toIndexPath:]` that causes this, swapping it back fixes it for me: ``` diff diff --git a/HPReorderTableView/HPReorderTableView.m b/HPReorderTableView/HPReorderTableView.m index b7d3fc7..5709fb4...

So my patch above does re-introduce the behaviour I _think_ 59f025c73da6e9aac8fdb2b4520504a15445d132 was supposed to fix; that is, the cell being moved moves on top of the other cells. I fixed...

Hi @kuldeep13990, Did you wire up the textfield before using it? ``` swift let textField = UITextField(); let ezFormTextField = EZFormTextField(); ezFormTextField.useTextField(textField); ``` Rob

Hi @drekka, this one sounds familiar, I believe we've seen it before. I will go digging through our PR history, but just to confirm, are you using UserDefaults to share...

Thanks @Nemesisprime. I'll test it out when I have a few moments to spare and commit the fix.

Closed in favour of the v3 alpha 1 PR

I'd recommend https://github.com/apple/swift-distributed-tracing over the opentelemetry-swift port as that's where the Swift on Server ecosystem is moving.

I agree with the sentiment expressed here and believe better testing of swift-syntax compatibility is desirable. But based on the concerns raised above I don't believe this is the correct...