Polysemy: 1.9.0.0 released!
Things have evolved since the beginning of this series! Polysemy had two major releases: 1.8.0.0 and 1.9.0.0. Not a lot of things have evolved, but we… ...more
Things have evolved since the beginning of this series! Polysemy had two major releases: 1.8.0.0 and 1.9.0.0. Not a lot of things have evolved, but we… ...more
In my previous log I mentioned the hiring process I set up in my company. In order to hire someone I have to know few things: What's the applicant ba… ...more
While Plutus is the "main" entry-point for smart contracts on Cardano, the only requirement is to produce some Plutus Core, to be run on Car… ...more
As I'll soon change company, I think it's the right time to do a retrospective of these years as CTO, for the first time. (Note that, legally speaking… ...more
I was expecting this lecture for so long: testing. At the time of writing, testing utils are provided in Plutus.Model, as part of plutus-simple-model,… ...more
In our previous log, we ended up with a lot of interpreters: intrepretUserRegistration :: Member InternalUserEffect r => InterpreterFor UserRegistr… ...more
This weeks' lesson is focused on NFT (Non-fungible token), which are "tokens" (non-divisible, duplicable, or copyable). Cardano contains thr… ...more
In our previous log, we have seen that we had to problematics: Splitting effects by concerns Having one target implementation A way to mitigate that… ...more
Cardano smart contract's code is splitted in two parts: on-chain and off-chain On-chain code is executed during transaction/data blockchain incorporat… ...more
After a while, it's tempting to have large effects, just because it's easier, or because they target one implementation. For example, in the codebases… ...more
Ouroboros is the consensus protocol powering Cardano. It is the first secured (and proven to be) proof-of-stake (PoS) blockchain protocol. Unlike proo… ...more
When it come to designing effects, an efficient way to know where to start is to look for IO (especially in embed/embedFinal). Let's have a look at a … ...more
Following the Plutus Pioneers Program 1st & 2nd lectures, this one takes a step closer to real world use cases. We are able to tests validators, l… ...more
Polysemy comes with many functions and interpreters relying on -threaded. However, whenever an issue (such as an Error) happens: failing :: Members … ...more
For a long time I have been interested in blockchain ecosystem for multiple reasons: A wide range of applications A very innovative field Lots of adv… ...more
In previous logs we have seen how to build interpreters thanks to Strategy. data BindE (m :: Type -> Type) a where BindE :: m a -> (a -> m … ...more
Polysemy provides some interpreters changing the returned value: runWriter :: Monoid o => Sem (Writer o ': r) a -> Sem r (o, a) The easiest… ...more
Polysemy provides many ways to combine both effects and interpreters, let's start with a simple Db effects: data Db (m :: Type -> Type) a where E… ...more
As seen in a previous log, some effects allow type classes to be supported. To enable Applicative, there is the NonDet effect, which works with Error … ...more
One of the effect used over and over again in our previous example is State, however, it's lack of atomicity can cause problems: incHundred :: Members… ...more
As part of the Haskell folklore, Polysemy supports MonadFix for with Fixpoint. Let's imagine a usecase where we want to find the sources of a source: … ...more
Polysemy comes with an useful effect to group other effects: Bundle. It comes with a useful function: sendBundle :: forall e r' r a. (Member e r… ...more
In a previous log, we saw that we are able to call other interpreters during interpretations. interpretBindTactic :: InterpreterFor BindE r interpretB… ...more
In a previous log, we introduce Final as an alternative to Embed. If we look at the intents: Embed aims to lift any Monad to Sem Final aims to embed … ...more
In a previous log, we ended with a solution for Resource which wasn't Error resistant. The solution is to use the soo-deperecated withLowerToIO. Let's… ...more
In a previous log, we introduced bindS providing a way to bind higher-order effects. Tactics also provide *T equivalent, starting with our example: da… ...more
In a previous log, we introduced liftS and runS which helps running higher-order effects in the interpretation Monad. However, you sometime have effec… ...more
Polysemy comes with many effects, today we'll have a look at Async which is the effect for and over async package. It enables running and driving asyn… ...more
In a previous log, we introduced Higher-order effects definition and interpretation through tactics. Some elements from tactics are already deprecated… ...more
In a previous log, we introduced Higher-order effects definition and interpretation through tactics. We'll see in another log an alternative way to de… ...more
One thing that sets polysemy apart is that it allows defining Higher-order effects. As higher-order functions, higher-order effects are effects define… ...more
Whenever you might have varying strategies to fetch some data, you might want to use Input: data Input i m a where Input :: Input i m i it comes wi… ...more