I have a string: let input = "Some text with <strong>an important part</strong>, then regular text." + " <strong>finally more im...

Hello there, I know TCA is where most of your efforts are these days, but I've been rewatching your parsing collection and have run into a block. I'm hoping you can get me past that...

http://2014.funswiftconf.com

[Continuations generalize] the asynchronous value concept. If we plug in `R = Void` then we just get an [asynchronous] value, but if we use a non-`Void` `R` value[,] we will get a type that kind of mixes together aspects of synchronous computation and asynchronous computation

This PR introduces some concept that were done by our friends at PointFree ❤️ combine and pullback for Reducer and Feedback Store class that has minimal set up of the state machine Context is abil...

Protocol-oriented programming is strongly recommended in the Swift community, and Apple has given a lot of guidance on how to use it in your everyday code. However, there has not been a lot of attention on when it is not appropriate, and what to do in that case. We will explore this idea, and show that there is a completely straightforward and mechanical way to translate any protocol into a concrete datatype. Once you do this you can still write your code much like you would with protocols, but all of the complexity inherit in protocols go away. Even more amazing, a new type of composition appears that is difficult to see when dealing with only protocols. We will also demo a real life, open source library that was originally written in the protocol-oriented way, but after running into many problems with the protocols, it was rewritten entirely in this witness-oriented way. The outcome was really surprising, and really powerful. https://twitter.com/mbrandonw https://appbuilders.ch

Swift’s generic functions allow us to explore a beautiful idea that straddles the line between mathematics and computer science

Given the following definition of `Prism`: ```swift struct Prism { let preview: (A) - B? let review: (B) - A } ```

Video: https://www.youtube.com/watch?v=A0VaIKK2ijM

“Category Theory is the greatest refactor of mathematics in history.”

“Look up pullbacks in differential geometry and you will find the image on the left. Look up pullbacks in category theory and you will find the image on the right, which generalizes everything in one diagram. That is the type of generality that libraries should strive for.”

I begin to feel that I can trust mathematics as a guiding beacon for how programming can be done well. This is why I feel strongly that simple mathematical constructs, like pure functions, monoids, etc., form a strong foundation of abstraction as opposed to the overly complicated, and often ad-hoc, design patterns we see in software engineering. ​ I spend a lot of my time trying to find new and creative ways to bring seemingly complex functional programming ideas down to earth and make them approachable to a wider audience. ​ but it does give us an opportunity to explore a strange and surprising result in computation and mathematics. It can help show that the connection between the two topics is perhaps deeper than we may first think.

Check out @mbrandonw's talk on how reducers compose, which covers how you can build up with a big ole "appReducer" out of all the smaller reducers in your code base:https://t.co/VFkcZyVxrr— Stephen Celis (@stephencelis) October 20, 2018

All of my math stuff from grad school. Contribute to mbrandonw/my-math-notes development by creating an account on GitHub.

http://2015.funswiftconf.com