The below is an off-site archive of all tweets posted by @mjtsai ever

June 19th, 2015

@marcoarment I never used to get that, now get it every time.

via Tweetbot for Mac in reply to marcoarment

@dnanian @adamengst No, first I was using a Dual-Link DVI display, now DisplayPort.

via Tweetbot for Mac in reply to dnanian

@iTod @owensd But certainly there is some room here for personal preference, and your example is better than others I've seen.

via Tweetbot for Mac in reply to mjtsai

@iTod @owensd I'm not a fan of the extra lines at the top to declare the variables, the extra indentation, or repeating the return value.

via Tweetbot for Mac in reply to iTod

@adamengst That is interesting that sleep helps. That wouldn't work for me because it was happening during long-running backups.

via Tweetbot for Mac in reply to adamengst

@iTod I knew about it, but when there are multiple things to clean up, try/finally is so awkward that people use goto and multiple labels.

via Tweetbot for Mac in reply to iTod

@iTod Yes, if we're talking about runtime behavior, and we have zero-cost exceptions. But I thought we were talking about codegen.

via Tweetbot for Mac in reply to iTod

@iTod @owensd @cananito I don't really think finally is finer-grained. Can't you achieve the same thing with defer by introducing a scope?

via Tweetbot for Mac in reply to iTod

@iTod Haven't looked at the assembly, but I would assume yes because try/finally has to essentially catch and rethrow the exception.

via Tweetbot for Mac in reply to iTod

@iTod Yes, mainly the syntax is much more convenient and readable. And there is the codegen difference because it’s not based on exceptions.

via Tweetbot for Mac in reply to iTod

@iTod Keep related blocks of code together.

via Tweetbot for Mac in reply to iTod

Swift 2 Error Handling, Continued: mjtsai.com/blog/2015/06/1…

via IFTTT