Vittorio Monaco

Hi @Carpemeid, thanks for the very detailed description of the issue you're encountering! To be honest, I have little time to investigate this in the short term, but I'll try...

I think we're going to properly fork this repo, add the 'L' block type support, and open a PR. Will mention it here!

We forked the repo, you can find our version here https://github.com/vittoriom/Light-Untar-for-iOS The PR for the long filename support is here https://github.com/mhausherr/Light-Untar-for-iOS/pull/27 ;)

Postponed due to infrastructure issues on Travis side (no Xcode 5, no iOS 7)

https://www.mikeash.com/pyblog/friday-qa-2014-01-10-lets-break-cocoa.html explains how to achieve this

Code snippet is: Caller Inspection The compiler builtin __builtin_return_address will give you the address of the code that called you: ``` void *addr = __builtin_return_address(0); ``` From that, we can...

Useful information at http://linux.die.net/man/3/dlopen Public Attributes of the struct: ``` const char * dli_fname void * dli_fbase const char * dli_sname void * dli_saddr int dli_version int dli_reserved1 long dli_reserved...

@stanislaw I'm glad you're interested in this kind of things! If you know something more about inspecting the caller, help is welcome! :)

_From @bkase on April 13, 2016 5:55_ Hi! I have some ideas: How about supplying the Future rather than the specific output type in a `CacheLevel`? Then you still only...

Hi @bkase , thanks for your suggestion! I'm a bit confused though how I could constrain the `AsyncOutputType` associatedtype of `CacheLevel` to be a `Future`. I actually need that to...