Comments (2)
This is mainly an issue of key paths taking longer when not qualified. Try recompiling stackView
by qualifying at least one of the root types:
var stackView = with(UIStackView(), concat(
mut(\UIStackView.axis, .vertical),
mut(\.isLayoutMarginsRelativeArrangement, true),
mut(\.layoutMargins, UIEdgeInsets(top: 0, left: 16, bottom: 0, right: 16)),
mut(\.spacing, 16),
mut(\.alignment, .center)
))
You can go so far as to qualify all root types to get a massive speedup:
var stackView = with(UIStackView(), concat(
mut(\UIStackView.axis, .vertical),
mut(\UIStackView.isLayoutMarginsRelativeArrangement, true),
mut(\UIStackView.layoutMargins, UIEdgeInsets(top: 0, left: 16, bottom: 0, right: 16)),
mut(\UIStackView.spacing, 16),
mut(\UIStackView.alignment, .center)
))
I think this is worth filing a bug at bugs.swift.org, though, as they should be able to make some optimizations here.
from swift-overture.
Hey @jonchui, we're going to close this out, but it's definitely an issue. One thing you could also try is to not use lazy
, which tends to put a lot of pressure on the type checker. Usually the way lazy
is used is not really saving too much work since most of a view's properties are probably accessed immediately.
Also filing bugs at bugs.swift.org can always help. The type checker has definitely gotten better over the years and these use cases provide great real-world examples.
from swift-overture.
Related Issues (18)
- Consider a more 'swifty' API HOT 4
- zip(with:) are not public ? HOT 1
- iOS target for Carthage HOT 5
- Ambiguous use of `with` HOT 2
- Redefine `set` without `over` HOT 1
- Add Info.plist HOT 1
- Currying higher order functions obscures type. HOT 2
- Add zip to Result HOT 1
- getting EXC_BAD_ACCESS while calling overture methods in static vars HOT 3
- Adding the operators counterpart HOT 5
- `with` is different from how it's portrayed in readme HOT 3
- Compilation failure using mut on a navigation controller HOT 1
- Is there a better way to style UINavigation's bar appearance?
- Add @discardableResult to update() HOT 4
- Potentially add `rethrows` to `over` and similar functions
- Xcode requiring `@escaping` for closure passed to `update` HOT 1
- Throwing overloads HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from swift-overture.