Add support for updateConstraints to match Masonry functionality. about snapkit

[robertjpayne]

We’ve explicitly left this out for now, it's actually been quite a source of headaches in Masonry as I believe is still not always dependable.

I personally recommend always using remake constraints and re-applying all the constraints you need. You can also always just use remakeConstraints ( the first time it just removes nothing so no errors ).

@cloudkite What's your thoughts on updateConstraints theseadays?

[mariohahn]

remake isn't the way to go because of performance issues, for example if you remake some constraints in a Tableviewcell.

[devxoul]

remake costs too expensive.

[cnoon]

Any progress here?

[robertjpayne]

@cnoon you can grab it in develop now. And to anyone else it's ready to go granted I've not tested it extensively so any help there is greatly appreciated.

Let me know how the performance is, it has the same logic as Masonry so it should perform similarly but it could definitely be improved.

[cnoon]

This is great @robertjpayne! We'll definitely give it some extensive testing over the next few weeks. On another note, thanks for all the activity and updates in the last week. We absolutely love using Snappy and really appreciate all your awesome work!