Search Results for "memory"

Cache doesn't claim to be unique in this area, but it's not another monster library that gives you a god's power. It does nothing but caching, but it does it well. It offers a good public API with out-of-box implementations and great customization possibilities. Cache utilizes Codable in Swift 4 to perform serialization. The cache is built based on a Chain-of-responsibility pattern, in which there are many processing objects, each knows how to do 1 task and delegates to the next one, so can...

...Asynchronous image downloading and caching. Loading image from either URLSession-based networking or local provided data. Useful image processors and filters provided. Multiple-layer hybrid cache for both memory and disk. Fine control on cache behavior. Customizable expiration date and size limit. Cancelable downloading and auto-reusing previous downloaded content to improve performance. Independent components. Use the downloader, caching system, and image processors separately as you need. Prefetching images and showing them from the cache to boost your app. ...

This repository collects a broad, categorized list of interview questions (with expected answers) that are commonly asked in iOS or Swift engineering interviews. Topics range from language fundamentals (memory management, ARC, value vs. reference types), to UIKit/SwiftUI, concurrency, Grand Central Dispatch, background execution, networking, design patterns, system frameworks, and architecture decisions. Each question is usually backed by sample explanations or code snippets, helping candidates understand not just what to answer but why it matters and how to reason about tradeoffs. ...

...Tesseract is written in C++ and over 30 years old. To use it you first have to write a Objective-C++ wrapper for it. The main issue that's slowing down Tesseract is the way memory is managed. Too many memory allocations and releases slow it down.

...Compared with others, the most significant feature of HandyJSON is that it does not require the objects inherit from NSObject(not using KVC but reflection), nor implements a 'mapping' function(writing value to memory directly to achieve property assignment). HandyJSON is totally dependent on the memory layout rules inferred from Swift runtime code. We are watching it and will follow every bit if it changes. To support deserialization from JSON, a class/struct needs to conform to 'HandyJSON' protocol. It's truly protocol, not some class inherited from NSObject. ...